•   
  • 1
  • 4
  • 5
  • 6(current)
  • 7
  • 8
  • 339
  •   
Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server
#76
(2015-07-17, 11:47)fritsch Wrote: If your remove the kodi.bin from the autostart file, does the xserver alone come up?

Try that please and get me: DISPLAY=:0 glxinfo | pastebinit

I see a very strange kernel error on your side - can you try with the shipped 3.19 kernel of Vivid?

OpenELEC from USB stick works?

I removed the kodi.bin but the xserver does not come up

DISPLAY=:0 glxinfo | pastebinit
http://paste.ubuntu.com/11892036/

I see a very strange kernel error on your side - can you try with the shipped 3.19 kernel of Vivid?
Same problem.


OpenELEC from USB stick works?
not tried yet, is the OpenELEC a live stick ?

kind regards
Reply
#77
Yes, gunzip the img.gz then dd it to an usb stick. On boot enter "live" without the "".
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#78
Please triple verify, that you did not forget the: dpkg-reconfigure x11-common to set it to everybody.

Also get me the user name you are using and the output of "id" with that user.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#79
The openelec stick works,

dpkg-reconfigure x11-commom is set to everybody , i have installed everthing with user kodi with id kodi
Reply
#80
I did some more testing and if i connect the pc with vga to a monitor i see everything (bios,prompt and then kodi)

When I connect with hdmi is see the following: bios ,prompt and then nothing

When I connect hdmi and vga , I see on the hdmi monitor :bios, prompt and then kodi on the vga monitor
Reply
#81
Quote:BOOT_IMAGE=/vmlinuz-4.1.2-040102-generic root=/dev/mapper/htpc--vg-root ro

You don't use encrypted homes, do you? From the dmesg it seems the GPU has issues with your HDMI monitor and it cannot determine its size. As it does not work with normal ubuntu either, it seems to be a bug, that you need to file at bugs.freedesktop.org cause it is sadly unrelated to the code we are testing here.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#82
Before filing, you can of course try:

Code:
mkdir kernel-drm
cd kernel-drm
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/linux-headers-4.2.0-994-generic_4.2.0-994.201507170159_amd64.deb
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/linux-headers-4.2.0-994_4.2.0-994.201507170159_all.deb
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/linux-image-4.2.0-994-generic_4.2.0-994.201507170159_amd64.deb
sudo dpkg -i *deb

Have fun.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#83
(2015-07-17, 13:39)fritsch Wrote: Before filing, you can of course try:

Code:
mkdir kernel-drm
cd kernel-drm
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/linux-headers-4.2.0-994-generic_4.2.0-994.201507170159_amd64.deb
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/linux-headers-4.2.0-994_4.2.0-994.201507170159_all.deb
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/linux-image-4.2.0-994-generic_4.2.0-994.201507170159_amd64.deb
sudo dpkg -i *deb

Have fun.

I have no encrypted homes and did run the kernal update but still the same problem, will report it @ bugs.freedesktop.org
Reply
#84
Btw. did this ever work for you? :-) What hardware is that?

Edit:
Quote:[ 0.063471] smpboot: CPU0: Intel® Core™ i5-3450 CPU @ 3.10GHz (fam: 06, model: 3a, stepping: 09)
[ 0.063490] Performance Events: PEBS fmt1+, 16-deep LBR, IvyBridge events, full-width counters, Intel PMU driver.

Should work ™.

What reveiled the OpenELEC test?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#85
I talked with chris wilson on IRC, have a look here: https://bugs.freedesktop.org/show_bug.cgi?id=88331 and subscribe yourself.

chris added a patch that fix it for you: https://bugs.freedesktop.org/show_bug.cgi?id=88331 <- though you need to build linux kernel from source and applying that patch manually.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#86
(2015-07-17, 14:07)fritsch Wrote: Btw. did this ever work for you? :-) What hardware is that?

Edit:
Quote:[ 0.063471] smpboot: CPU0: Intel® Core™ i5-3450 CPU @ 3.10GHz (fam: 06, model: 3a, stepping: 09)
[ 0.063490] Performance Events: PEBS fmt1+, 16-deep LBR, IvyBridge events, full-width counters, Intel PMU driver.

Should work ™.

What reveiled the OpenELEC test?

It worked with this tutorial : http://forum.kodi.tv/showthread.php?tid=165707 , the hardware is a dell OptiPlex 3010

With openelec it worked !
Reply
#87
(2015-07-17, 14:18)fritsch Wrote: I talked with chris wilson on IRC, have a look here: https://bugs.freedesktop.org/show_bug.cgi?id=88331 and subscribe yourself.

chris added a patch that fix it for you: https://bugs.freedesktop.org/show_bug.cgi?id=88331 <- though you need to build linux kernel from source and applying that patch manually.

Thanks for the asking on IRC but my knowledge of Linux is to so great that I can compile a linux kernal ;-(
Reply
#88
Then there is still something wrong with the initial setup, as OpenELEC (the builds I provide here) use the very same kernel (4.1.x).

Get me again:
id | pastebinit

then do:
sudo systemctl stop kodi

and afterwards
X &
DISPLAY=:0 kodi

Edit: And as you are at it, get me: sudo journalctl -a | pastebinit too
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#89
[quote='fritsch' pid='2054970' dateline='1437139407']
Then there is still something wrong with the initial setup, as OpenELEC (the builds I provide here) use the very same kernel (4.1.x).


id | pastebinit
http://paste.ubuntu.com/11892840/


sudo systemctl stop kodi


X &
DISPLAY=:0 kodi
[email protected]:~$ X &
[1] 1160
[email protected]:~$ DISPLAY=:0 kodi
X.Org X Server 1.17.1
Release Date: 2015-02-10
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu
Current Operating System: Linux htpc 4.2.0-994-generic #201507170159 SMP Fri Jul 17 02:01:25 UTC 2015 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-4.2.0-994-generic root=/dev/mapper/htpc--vg-root ro
Build Date: 19 March 2015 09:26:59AM
xorg-server 2:1.17.1-0ubuntu3 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.32.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Jul 17 15:45:22 2015
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server

but no screen output to hdmi

[email protected]:~$ sudo journalctl -a | pastebinit
Traceback (most recent call last):
File "/usr/bin/pastebinit", line 345, in <module>
content = sys.stdin.read()
File "/usr/lib/python3.4/codecs.py", line 319, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa6 in position 12429: invalid start byte
[email protected]:~$ sudo journalctl -a | pastebinit
Traceback (most recent call last):
File "/usr/bin/pastebinit", line 345, in <module>
content = sys.stdin.read()
File "/usr/lib/python3.4/codecs.py", line 319, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa6 in position 12429: invalid start byte
Reply
#90
Yeah, then you need to upload the journalctl -a > debug.txt somewhere.

But I think you are affected by the bug mentioned above, so it won't work.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
  •   
  • 1
  • 4
  • 5
  • 6(current)
  • 7
  • 8
  • 339
  •   



Logout Mark Read Team Forum Stats Members Help
Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server18
This forum uses Lukasz Tkacz MyBB addons.