[opensuse] Zotac Nano CI323: X problems and Intel i915 (Intel Corporation Device 22b1)
Continuation of my installation report on the Zotac Nano CI323. Note - we're talking openSUSE 12.3, but with newer 3.16.7/4.x kernels. When running mythtv with SD content, the video stutters. Given that my ancient IBM SFF desktop with a much less capable config has no problems with SD content and manages quite well with HD content, something isn't right. Now, it's been a while since I've had to fiddle with graphics and X config and such, but AFAIR there's no need for xorg.conf anymore. Well, that didn't work for me with this one - initially I got no X, so after researching the problem, I copied xorg.conf.install to xorg.conf which at least gave me X. This is now the config that gives me less-than-adequate performance with mythtv. I've studied that xorg.conf some, and it looks like it isn't in fact using the Intel driver? http://files.jessen.ch/zotac1-xorg.conf.install I'm guessing it's probably just running with fbdev?
From advice found <somewhere>, I've added /etc/X11/xorg.d.conf/20-intel.conf:
Section "Device" Identifier "Intel Graphics" Driver "intel" EndSection This didn't do much good either. Here is the Xorg.0.log: http://files.jessen.ch/zotac1-Xorg.0.log.txt (II) UnloadModule: "intel" (EE) Screen(s) found, but none have a usable configuration. Suggestions, please. -- Per Jessen, Zürich (11.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
I've studied that xorg.conf some, and it looks like it isn't in fact using the Intel driver?
http://files.jessen.ch/zotac1-xorg.conf.install
I'm guessing it's probably just running with fbdev?
From advice found <somewhere>, I've added /etc/X11/xorg.d.conf/20-intel.conf:
Section "Device" Identifier "Intel Graphics" Driver "intel" EndSection
This didn't do much good either. Here is the Xorg.0.log: http://files.jessen.ch/zotac1-Xorg.0.log.txt
I'm not really very knowledgeable when it comes this X-stuff, can anyone suggest a way to proceed? The machine works fine, but to get decent graphics performance it seem to me I need to get it work with the intel driver.
(II) UnloadModule: "intel" (EE) Screen(s) found, but none have a usable configuration.
This seems to be the key error message, but what does it mean? -- Per Jessen, Zürich (9.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op dinsdag 22 maart 2016 14:31:08 schreef Per Jessen:
Per Jessen wrote:
I've studied that xorg.conf some, and it looks like it isn't in fact using the Intel driver?
http://files.jessen.ch/zotac1-xorg.conf.install
I'm guessing it's probably just running with fbdev?
From advice found <somewhere>, I've
added /etc/X11/xorg.d.conf/20-intel.conf:
Section "Device"
Identifier "Intel Graphics" Driver "intel"
EndSection
This didn't do much good either. Here is the Xorg.0.log: http://files.jessen.ch/zotac1-Xorg.0.log.txt
I'm not really very knowledgeable when it comes this X-stuff, can anyone suggest a way to proceed? The machine works fine, but to get decent graphics performance it seem to me I need to get it work with the intel driver.
(II) UnloadModule: "intel" (EE) Screen(s) found, but none have a usable configuration.
This seems to be the key error message, but what does it mean?
I also have problems with the Intel graphics i915 in my laptop, Using openSUSE 13.2 and Tumbleweed, I need to add nomodeset to the boot-line. However openSUSE Leap 42.1 works without nomodeset. The only solution seems to the nomodeset. See also http://bugzilla.suse.com/show_bug.cgi?id=899879 However your problem seems to be different. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Freek de Kruijf wrote:
Op dinsdag 22 maart 2016 14:31:08 schreef Per Jessen:
Per Jessen wrote:
I've studied that xorg.conf some, and it looks like it isn't in fact using the Intel driver?
http://files.jessen.ch/zotac1-xorg.conf.install
I'm guessing it's probably just running with fbdev?
From advice found <somewhere>, I've
added /etc/X11/xorg.d.conf/20-intel.conf:
Section "Device"
Identifier "Intel Graphics" Driver "intel"
EndSection
This didn't do much good either. Here is the Xorg.0.log: http://files.jessen.ch/zotac1-Xorg.0.log.txt
I'm not really very knowledgeable when it comes this X-stuff, can anyone suggest a way to proceed? The machine works fine, but to get decent graphics performance it seem to me I need to get it work with the intel driver.
(II) UnloadModule: "intel" (EE) Screen(s) found, but none have a usable configuration.
This seems to be the key error message, but what does it mean?
I also have problems with the Intel graphics i915 in my laptop, Using openSUSE 13.2 and Tumbleweed, I need to add nomodeset to the boot-line. However openSUSE Leap 42.1 works without nomodeset. The only solution seems to the nomodeset.
See also http://bugzilla.suse.com/show_bug.cgi?id=899879
However your problem seems to be different.
I can also make it work with nomodeset, but performance+resolution just isn't good enough. -- Per Jessen, Zürich (10.2°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen composed on 2016-03-22 14:31 (UTC+0100):
Per Jessen wrote:
I've studied that xorg.conf some, and it looks like it isn't in fact using the Intel driver?
I'm guessing it's probably just running with fbdev?
From advice found <somewhere>, I've added /etc/X11/xorg.d.conf/20-intel.conf:
Section "Device" Identifier "Intel Graphics" Driver "intel" EndSection
This didn't do much good either. Here is the Xorg.0.log: http://files.jessen.ch/zotac1-Xorg.0.log.txt
I'm not really very knowledgeable when it comes this X-stuff, can anyone suggest a way to proceed? The machine works fine, but to get decent graphics performance it seem to me I need to get it work with the intel driver.
(II) UnloadModule: "intel" (EE) Screen(s) found, but none have a usable configuration.
This seems to be the key error message, but what does it mean?
Take a look at /etc/X11/xorg.conf.d/50-screen.conf and you should see why - everything in it is comments. For /etc/X11/xorg.d.conf/20-intel.conf to have any effect, /etc/X11/xorg.d.conf/ must contain corresponding device, monitor and screen sections, as the entirely commented July 2011 example files 50-device.conf 50-monitor.conf 50-screen.conf in /etc/X11/xorg.d.conf/ try to show. So rather than creating 20-intel.conf, uncomment the needed parts of those three files, so that they look as follows: # 50-device.conf Section "Device" Identifier "DefaultDevice" Driver "intel" EndSection # 50-monitor.conf Section "Monitor" Identifier "DefaultMonitor" EndSection # 50-screen.conf Section "Screen" Identifier "DefaultScreen" Device "DefaultDevice" Monitor "DefaultMonitor" EndSection Alternatively, remove your 20-intel.conf file, then copy and paste the above in its entirety as /etc/X11/xorg.conf. If using it Xorg.0.log still does not show that the intel(0): driver is being used, share the new Xorg.0.log. The Intel driver ought to just work without any configs provided in /etc/X11/, so maybe first we should see what Xorg.0.log looks like without any existing. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata wrote:
Take a look at /etc/X11/xorg.conf.d/50-screen.conf and you should see why - everything in it is comments.
For /etc/X11/xorg.d.conf/20-intel.conf to have any effect, /etc/X11/xorg.d.conf/ must contain corresponding device, monitor and screen sections, as the entirely commented July 2011 example files
Okay, thanks.
50-device.conf 50-monitor.conf 50-screen.conf
I've removed 20-intel.conf and amended the files above: # grep -v ^# 50* 50-device.conf:Section "Device" 50-device.conf: Identifier "DefaultDevice" 50-device.conf: Driver "intel" 50-device.conf:EndSection 50-monitor.conf:Section "Monitor" 50-monitor.conf: Identifier "DefaultMonitor" 50-monitor.conf:EndSection 50-screen.conf:Section "Screen" 50-screen.conf: Identifier "DefaultScreen" 50-screen.conf: Device "DefaultDevice" 50-screen.conf: Monitor "DefaultMonitor" 50-screen.conf:EndSection
Alternatively, remove your 20-intel.conf file, then copy and paste the above in its entirety as /etc/X11/xorg.conf. If using it Xorg.0.log still does not show that the intel(0): driver is being used, share the new Xorg.0.log.
With the config above, the system starts and I even see three lines of output on VT7, but no GUI. Here is the xorg.0.log from that first attempt: http://files.jessen.ch/zotac-xorg.0.log-20160323-001.txt Just in case, this is the dmesg output: http://files.jessen.ch/zotac-dmesg-20160323-001.txt -- Per Jessen, Zürich (3.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen composed on 2016-03-23 08:35 (UTC+0100): (re: Zotac Nano CI323)
With the config above, the system starts and I even see three lines of output on VT7, but no GUI.
Here is the xorg.0.log from that first attempt: http://files.jessen.ch/zotac-xorg.0.log-20160323-001.txt
X.Org X Server 1.13.2 Release Date: 2013-01-24
Just in case, this is the dmesg output: http://files.jessen.ch/zotac-dmesg-20160323-001.txt
Whatever did you see that suggests you're going to get an operating system released 2 years before the machine you are using was probably designed? Server 1.13.2 is 12.3, which was released 3 years ago. Dmesg indicates PC "BIOS" date is 2016. Even 42.1 might not be new enough. I know next to nothing about updating an ancient OS for newer hardware. Maybe with newer kernel, and newer kernel-firmware, and much more recent Xorg and Intel driver, and maybe compiling it all yourself, it's possible, but good luck trying. I can't envision any way out of being stuck using a slow as molasses generic video driver rather than a proper Intel driver if you insist on sticking with 12.3. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata wrote:
Per Jessen composed on 2016-03-23 08:35 (UTC+0100):
(re: Zotac Nano CI323)
With the config above, the system starts and I even see three lines of output on VT7, but no GUI.
Here is the xorg.0.log from that first attempt: http://files.jessen.ch/zotac-xorg.0.log-20160323-001.txt
X.Org X Server 1.13.2 Release Date: 2013-01-24
Just in case, this is the dmesg output: http://files.jessen.ch/zotac-dmesg-20160323-001.txt
Whatever did you see that suggests you're going to get an operating system released 2 years before the machine you are using was probably designed? Server 1.13.2 is 12.3, which was released 3 years ago. Dmesg indicates PC "BIOS" date is 2016. Even 42.1 might not be new enough. I know next to nothing about updating an ancient OS for newer hardware.
Unfortunately I need to remain on openSUSE 12.3. MythTV needs matching frontends and backends, and 0.25 is not available on newer OS. I tried building it myself, but in the end it looked much easier to just install openSUSE 12.3.
Maybe with newer kernel, and newer kernel-firmware, and much more
Yes, which I have already installed, the machine works very well with both 4.1 and 4.5. I run 4.1 by default.
recent Xorg and Intel driver,
The Intel driver is the latest and greatest. -- Per Jessen, Zürich (6.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Unfortunately I need to remain on openSUSE 12.3. MythTV needs matching frontends and backends, and 0.25 is not available on newer OS. I tried building it myself, but in the end it looked much easier to just install openSUSE 12.3.
Maybe with newer kernel, and newer kernel-firmware, and much more
Yes, which I have already installed, the machine works very well with both 4.1 and 4.5. I run 4.1 by default.
recent Xorg and Intel driver,
The Intel driver is the latest and greatest.
Now running with 4.5.0-2.gc2c16d5-default, I spotted something else in the dmesg output: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe C FIFO underrun Googling that led me to: https://bugs.freedesktop.org/show_bug.cgi?id=89806 It isn't totally clear if it's been fixed in 4.5. Ah well. Does anyone have a smallish livingroom PC a la this Zotac but a couple of years old? I'll swap you. Gee, all this hassle just because SFDRS switched to HD-only satellite feed. -- Per Jessen, Zürich (6.7°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen composed on 2016-03-23 10:25 (UTC+0100):
Unfortunately I need to remain on openSUSE 12.3. MythTV needs matching frontends and backends, and 0.25 is not available on newer OS. I tried building it myself, but in the end it looked much easier to just install openSUSE 12.3.
Maybe with newer kernel, and newer kernel-firmware, and much more
Yes, which I have already installed, the machine works very well with both 4.1 and 4.5. I run 4.1 by default.
Kernel 4.1 and 4.5 only, or those two plus the newest kernel-firmware?
recent Xorg and Intel driver,
The Intel driver is the latest and greatest.
Does "driver" mean the whole set, xf86-video-intel-2.99.917.x plus libdrm2_intel1 and whatever it depends on? And Xorg itself? Doesn't the Intel driver need to be matched to the actual Xorg version itself, which in your case is the ancient 1.13.2? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata wrote:
Per Jessen composed on 2016-03-23 10:25 (UTC+0100):
Unfortunately I need to remain on openSUSE 12.3. MythTV needs matching frontends and backends, and 0.25 is not available on newer OS. I tried building it myself, but in the end it looked much easier to just install openSUSE 12.3.
Maybe with newer kernel, and newer kernel-firmware, and much more
Yes, which I have already installed, the machine works very well with both 4.1 and 4.5. I run 4.1 by default.
Kernel 4.1 and 4.5 only, or those two plus the newest kernel-firmware?
I think so. The 4.1 kernel is from Leap 42.1, the firmware is kernel-firmware-20150925git-1.1.noarch - searching http://software.opensuse.org, I do see kernel-firmware-20160112git, I guess it might be worth a try too.
recent Xorg and Intel driver,
The Intel driver is the latest and greatest.
Does "driver" mean the whole set, xf86-video-intel-2.99.917.x plus libdrm2_intel1 and whatever it depends on?
Hmm, I was really only thinking of the kernel driver. # rpm -qa | grep intel vaapi-intel-driver-1.0.19-2.1.1.x86_64 libdrm_intel1-2.4.42-1.1.1.x86_64 intel-gpu-tools-1.3-2.1.1.x86_64 xf86-video-intel-2.20.19-2.1.1.x86_64 This is obviously way back-level. I'll see if any of it can be updated.
And Xorg itself? Doesn't the Intel driver need to be matched to the actual Xorg version itself, which in your case is the ancient 1.13.2?
If you mean "Intel driver" as in the collection of packages above, yes quite possibly. -- Per Jessen, Zürich (7.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Felix Miata wrote:
Does "driver" mean the whole set, xf86-video-intel-2.99.917.x plus libdrm2_intel1 and whatever it depends on?
Hmm, I was really only thinking of the kernel driver.
# rpm -qa | grep intel vaapi-intel-driver-1.0.19-2.1.1.x86_64 libdrm_intel1-2.4.42-1.1.1.x86_64 intel-gpu-tools-1.3-2.1.1.x86_64 xf86-video-intel-2.20.19-2.1.1.x86_64
This is obviously way back-level. I'll see if any of it can be updated.
Well, that went much smoother than anticipated - to start with I upgraded to whatever was the current in 13.1. This does seem to have improved things significantly: <-------- # grep intel /var/log/Xorg.0.log [ 37.831] (II) LoadModule: "intel" [ 37.846] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so [ 37.851] (II) Module intel: vendor="X.Org Foundation" [ 37.851] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: [ 37.879] (II) intel(0): Creating default Display subsection in Screen section [ 37.879] (==) intel(0): Depth 24, (--) framebuffer bpp 32 [ 37.879] (==) intel(0): RGB weight 888 [ 37.879] (==) intel(0): Default visual is TrueColor [ 37.880] (WW) intel(0): Unknown chipset [ 37.880] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2 [ 37.880] (**) intel(0): Framebuffer tiled [ 37.880] (**) intel(0): Pixmaps tiled [ 37.880] (**) intel(0): "Tear free" disabled [ 37.880] (**) intel(0): Forcing per-crtc-pixmaps? no [ 37.881] (II) intel(0): Output HDMI1 using monitor section DefaultMonitor [ 37.881] (II) intel(0): Output DP1 has no monitor section [ 37.881] (II) intel(0): Output HDMI2 has no monitor section [ 37.881] (II) intel(0): Output DP2 has no monitor section [ 37.881] (II) intel(0): Output VIRTUAL1 has no monitor section [ 37.882] (--) intel(0): Output HDMI2 using initial mode 1920x1080 on pipe 2 [ 37.882] (==) intel(0): DPI set to (96, 96) [ 37.882] (II) intel(0): SNA initialized with generic backend [ 37.883] (==) intel(0): Backing store disabled [ 37.883] (==) intel(0): Silken mouse enabled [ 37.883] (II) intel(0): HW Cursor enabled [ 37.883] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message. [ 37.884] (==) intel(0): DPMS enabled [ 37.884] (II) intel(0): Textured video not supported on this hardware [ 37.885] (II) intel(0): [DRI2] Setup complete [ 37.885] (II) intel(0): [DRI2] DRI driver: i965 [ 37.885] (II) intel(0): direct rendering: DRI2 Enabled [ 37.885] (==) intel(0): hotplug detection: "enabled" [ 38.439] (II) intel(0): switch to mode 1920x1080@50.0 on pipe 2 using HDMI2, position (0, 0), rotation normal [ 38.444] (II) intel(0): Setting screen physical size to 508 x 285 [ 76.121] (II) intel(0): EDID vendor "TSB", prod id 267 [ 76.121] (II) intel(0): Using EDID range info for horizontal sync [ 76.121] (II) intel(0): Using EDID range info for vertical refresh [ 76.121] (II) intel(0): Printing DDC gathered Modelines: [ 76.121] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz eP) [ 76.121] (II) intel(0): Modeline "1360x768"x0.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e) [ 76.121] (II) intel(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e) [ 76.121] (II) intel(0): Modeline "1280x768"x0.0 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e) [ 76.122] (II) intel(0): Modeline "1280x768"x0.0 102.25 1280 1360 1488 1696 768 771 778 805 -hsync +vsync (60.3 kHz e) [ 76.122] (II) intel(0): Modeline "1280x768"x0.0 68.25 1280 1328 1360 1440 768 771 778 790 +hsync -vsync (47.4 kHz e) [ 76.122] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) [ 76.122] (II) intel(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) [ 76.122] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) [ 76.122] (II) intel(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) [ 76.122] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) [ 76.122] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) [ 76.122] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) [ 76.122] (II) intel(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) [ 76.122] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) [ 76.122] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) [ 76.122] (II) intel(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) [ 76.123] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) [ 76.123] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e) [ 76.123] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (28.1 kHz e) [ 76.123] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (33.8 kHz e) [ 76.123] (II) intel(0): Modeline "2880x480"x0.0 108.00 2880 2944 3192 3432 480 489 495 525 -hsync -vsync (31.5 kHz e) [ 76.123] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e) [ 76.123] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e) [ 76.123] (II) intel(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e) [ 76.123] (II) intel(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e) [ 76.123] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e) [ 76.123] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) [ 76.123] (II) intel(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) [ 76.123] (II) intel(0): Modeline "1440x288"x0.0 27.00 1440 1464 1590 1728 288 290 293 312 -hsync -vsync (15.6 kHz e) [ 76.124] (II) intel(0): Modeline "1440x240"x0.0 27.00 1440 1478 1602 1716 240 244 247 262 -hsync -vsync (15.7 kHz e) ---------> However - playing HDTV with mythTV still stutters. I can see two cores both running at almost 100%. Looking at the xorg.0.log some more: [ 38.239] (II) LoadModule: "intel" [ 38.255] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so [ 38.262] (II) Module intel: vendor="X.Org Foundation" [ 38.262] compiled for 1.14.3.901, module version = 2.99.906 [ 38.262] Module class: X.Org Video Driver [ 38.262] ABI class: X.Org Video Driver, version 14.1 [ 38.263] (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, HD Graphics, HD Graphics 2000, HD Graphics 3000, HD Graphics 2500, HD Graphics 4000, HD Graphics P4000, HD Graphics 4600, HD Graphics 5000, HD Graphics P4600/P4700, Iris(TM) Graphics 5100, HD Graphics 4400, HD Graphics 4200, Iris(TM) Pro Graphics 5200 [ 38.265] (++) using VT number 7 I seem to have a different set of chipsets listed when compared to earlier: [ 30.175] (II) LoadModule: "intel" [ 30.186] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so [ 30.190] (II) Module intel: vendor="X.Org Foundation" [ 30.190] compiled for 1.13.1, module version = 2.20.19 [ 30.190] Module class: X.Org Video Driver [ 30.190] ABI class: X.Org Video Driver, version 13.1 [ 30.190] (II) intel: Driver for Intel 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, B43, Clarkdale, Arrandale, Sandybridge Desktop (GT1), Sandybridge Desktop (GT2), Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1), Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+), Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2), Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server, Ivybridge Server (GT2), Haswell Desktop (GT1), Haswell Desktop (GT2), Haswell Desktop (GT2+), Haswell Mobile (GT1), Haswell Mobile (GT2), Haswell Mobile (GT2+), Haswell Server (GT1), Haswell Server (GT2), Haswell Server (GT2+), Haswell SDV Desktop (GT1), Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT2+), Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2), Haswell SDV Mobile (GT2+), Haswell SDV Server (GT1), Haswell SDV Server (GT2), Haswell SDV Server (GT2+), Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2), Haswell ULT Desktop (GT2+), Haswell ULT Mobile (GT1), Haswell ULT Mobile (GT2), Haswell ULT Mobile (GT2+), Haswell ULT Server (GT1), Haswell ULT Server (GT2), Haswell ULT Server (GT2+), Haswell CRW Desktop (GT1), Haswell CRW Desktop (GT2), Haswell CRW Desktop (GT2+), Haswell CRW Mobile (GT1), Haswell CRW Mobile (GT2), Haswell CRW Mobile (GT2+), Haswell CRW Server (GT1), Haswell CRW Server (GT2), Haswell CRW Server (GT2+), ValleyView PO board [ 30.191] (++) using VT number 7 -- Per Jessen, Zürich (7.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
However - playing HDTV with mythTV still stutters. I can see two cores both running at almost 100%.
Hmm, this whole thing may have been an exercise in futility. Some more digging has revealed that MythTV prefers using software decoding, i.e. with the system CPUs. That would be fine but the Zotac nano's quad cores at 1.6GHz apparently aren't enough for HDTV. Unless I can get hardware-assisted decoding to work (VAAPI), this box just isn't potent enough. My old (single 2.8GHz Celeron) desktop running the current tv system provides essentially the same performance (HDTV stutters) as the Zotac. -- Per Jessen, Zürich (6.7°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Per Jessen wrote:
However - playing HDTV with mythTV still stutters. I can see two cores both running at almost 100%. Hmm, this whole thing may have been an exercise in futility. Some more digging has revealed that MythTV prefers using software decoding, i.e. with the system CPUs. That would be fine but the Zotac nano's quad cores at 1.6GHz apparently aren't enough for HDTV. Unless I can get hardware-assisted decoding to work (VAAPI), this box just isn't potent enough. Have you checked this?
https://www.mythtv.org/wiki/VAAPI Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Bjoern Voigt wrote:
Per Jessen wrote:
Per Jessen wrote:
However - playing HDTV with mythTV still stutters. I can see two cores both running at almost 100%. Hmm, this whole thing may have been an exercise in futility. Some more digging has revealed that MythTV prefers using software decoding, i.e. with the system CPUs. That would be fine but the Zotac nano's quad cores at 1.6GHz apparently aren't enough for HDTV. Unless I can get hardware-assisted decoding to work (VAAPI), this box just isn't potent enough. Have you checked this?
Yep, I am just now looking at that. /Per -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/23/2016 06:34 AM, Per Jessen wrote:
Felix Miata wrote:
Per Jessen composed on 2016-03-23 10:25 (UTC+0100):
Unfortunately I need to remain on openSUSE 12.3. MythTV needs matching frontends and backends, and 0.25 is not available on newer OS. I tried building it myself, but in the end it looked much easier to just install openSUSE 12.3.
Maybe with newer kernel, and newer kernel-firmware, and much more
Yes, which I have already installed, the machine works very well with both 4.1 and 4.5. I run 4.1 by default.
Kernel 4.1 and 4.5 only, or those two plus the newest kernel-firmware?
I think so. The 4.1 kernel is from Leap 42.1, the firmware is kernel-firmware-20150925git-1.1.noarch - searching http://software.opensuse.org, I do see kernel-firmware-20160112git, I guess it might be worth a try too.
On my 13.1 dell machine I observe (though I'm not using) $ rpm -qf /lib/firmware/i915/ kernel-firmware-20160112git-35.1.noarch zypper info says for that Repository: kernel_Stable Name: kernel-firmware Version: 20160112git-35.1 Arch: noarch Vendor: obs://build.opensuse.org/Kernel Installed: Yes Status: up-to-date Installed Size: 120.3 MiB Summary: Linux kernel firmware files Description: This package contains the firmware for in-kernel drivers that was previously included in the kernel. It is shared by all kernels >= 2.6.27-rc1. Also in that package are the following, though I don't know what they are for and would appreciate enlightenment. /lib/firmware/i915/bxt_dmc_ver1.bin /lib/firmware/i915/bxt_dmc_ver1_04.bin /lib/firmware/i915/bxt_dmc_ver1_05.bin /lib/firmware/i915/bxt_dmc_ver1_06.bin /lib/firmware/i915/skl_dmc_ver1.bin /lib/firmware/i915/skl_dmc_ver1_23.bin /lib/firmware/i915/skl_guc_ver1.bin /lib/firmware/i915/skl_guc_ver1_1059.bin /lib/firmware/i915/skl_guc_ver4.bin /lib/firmware/i915/skl_guc_ver4_3.bin -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
On my 13.1 dell machine I observe (though I'm not using)
$ rpm -qf /lib/firmware/i915/ kernel-firmware-20160112git-35.1.noarch
Hmm, I wonder where you got that from. I don't see anyhting like that for 13.1.
Also in that package are the following, though I don't know what they are for and would appreciate enlightenment.
/lib/firmware/i915/bxt_dmc_ver1.bin /lib/firmware/i915/bxt_dmc_ver1_04.bin /lib/firmware/i915/bxt_dmc_ver1_05.bin /lib/firmware/i915/bxt_dmc_ver1_06.bin /lib/firmware/i915/skl_dmc_ver1.bin /lib/firmware/i915/skl_dmc_ver1_23.bin /lib/firmware/i915/skl_guc_ver1.bin /lib/firmware/i915/skl_guc_ver1_1059.bin /lib/firmware/i915/skl_guc_ver4.bin /lib/firmware/i915/skl_guc_ver4_3.bin
They are the actual firmware packages for certain Intel chipsets. -- Per Jessen, Zürich (6.4°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/23/2016 09:36 AM, Per Jessen wrote:
Anton Aylward wrote:
On my 13.1 dell machine I observe (though I'm not using)
$ rpm -qf /lib/firmware/i915/ kernel-firmware-20160112git-35.1.noarch Hmm, I wonder where you got that from. I don't see anyhting like that for 13.1.
I told you, from "kernel_Stable", Which I've mentioned MANY MANY times here before. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
On 03/23/2016 09:36 AM, Per Jessen wrote:
Anton Aylward wrote:
On my 13.1 dell machine I observe (though I'm not using)
$ rpm -qf /lib/firmware/i915/ kernel-firmware-20160112git-35.1.noarch Hmm, I wonder where you got that from. I don't see anyhting like that for 13.1.
I told you, from "kernel_Stable", Which I've mentioned MANY MANY times here before.
You probably have, but just as you no doubt don't recall any arbitrary config of mine nor do I recall any of yours :-) -- Per Jessen, Zürich (6.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/23/2016 10:17 AM, Per Jessen wrote:
Anton Aylward wrote:
On 03/23/2016 09:36 AM, Per Jessen wrote:
Anton Aylward wrote:
On my 13.1 dell machine I observe (though I'm not using)
$ rpm -qf /lib/firmware/i915/ kernel-firmware-20160112git-35.1.noarch Hmm, I wonder where you got that from. I don't see anyhting like that for 13.1.
I told you, from "kernel_Stable", Which I've mentioned MANY MANY times here before.
You probably have, but just as you no doubt don't recall any arbitrary config of mine nor do I recall any of yours :-)
Most recently; Message-ID: <56EBD910.3000308@antonaylward.com> Date: Fri, 18 Mar 2016 06:31:44 -0400 -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/23/2016 03:35 AM, Per Jessen wrote:
I've removed 20-intel.conf and amended the files above:
Good. That puts you on the "same page" as the rest of us "915 haters'. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/23/2016 03:35 AM, Per Jessen wrote:
Here is the xorg.0.log from that first attempt: http://files.jessen.ch/zotac-xorg.0.log-20160323-001.txt
It really does not like the "intel" driver you have"
Just in case, this is the dmesg output: http://files.jessen.ch/zotac-dmesg-20160323-001.txt
I note
[ 3.093370] [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor 0 [ 3.141069] [drm] GMBUS [i915 gmbus dpc] timed out, falling back to bit banging on pin 4 [ 3.211879] fbcon: inteldrmfb (fb0) is primary device [ 3.515272] [drm:valleyview_update_wm [i915]] *ERROR* timed out waiting for Punit DDR DVFS request
and finally its insisting on
[ 687.123881] [drm:valleyview_update_wm [i915]] *ERROR* timed out waiting for Punit DDR DVFS request
I see in a later post that Felix observes a disparity in datelines. Your chip and your driver are from very different "generations". I've mentioned already the problems I've had with chips of the same nominal 'generation' differing by a few (hundred) iterations, so i'm not surprised by this. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/22/2016 09:31 AM, Per Jessen wrote:
Per Jessen wrote:
I've studied that xorg.conf some, and it looks like it isn't in fact using the Intel driver?
http://files.jessen.ch/zotac1-xorg.conf.install
I'm guessing it's probably just running with fbdev?
From advice found <somewhere>, I've added /etc/X11/xorg.d.conf/20-intel.conf:
Section "Device" Identifier "Intel Graphics" Driver "intel" EndSection
This didn't do much good either. Here is the Xorg.0.log: http://files.jessen.ch/zotac1-Xorg.0.log.txt
I'm not really very knowledgeable when it comes this X-stuff, can anyone suggest a way to proceed? The machine works fine, but to get decent graphics performance it seem to me I need to get it work with the intel driver.
(II) UnloadModule: "intel" (EE) Screen(s) found, but none have a usable configuration.
This seems to be the key error message, but what does it mean?
Yes it is. I used the 915 with a machine that is now dead and offline. I can't find any specific notes so this is from memory. What that message means is that the parts don't match up properly A "Screen is made up out of * Monitor * Device * Display That is a definition of the characteristics of the monitor (q.v.), a definition of the GPU device, a definition of the display (think of that as the virtual screen area). if any of these don't make sense either at "compile" time or at "run" time, then you have a !FAIL! Sorry if I'm telling things you already know. TWO PATHS APPEAR TO ME ============== The First ===================== Now I have a $ sudo /sbin/lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express Integrated Graphics Controller (rev 02) and that uses the "intel" driver. When your X server tries loading the "intel" driver for your GPU it fails, somehow and unloads.
(II) UnloadModule: "intel"
That may be becuase you have one or more "Option" settings that it barfs on, but in this case I think you are wrong to use the "intel" driver. There is a 915 driver:
find /lib -name '*915*' /lib/modules/4.5.0-3.g8ec3d36-default/kernel/drivers/gpu/drm/i915 /lib/modules/4.5.0-3.g8ec3d36-default/kernel/drivers/gpu/drm/i915/i915.ko /lib/firmware/i915 /lib/firmware/LICENSE.i915
And that firmware. Have you tried using that? Yes there are a lot of bugs listed for the 915 driver, but that's the case, I see, for just about every other one :-( According the bug list the driver I'm using shouldn't work with my hardware. I've noticed that the installers (and Knoppix) seem to be able to probe and find out which driver to use quite effectively. Maybe see what they leave as 'debris files". A word of warning. The "Option" setting is a some kind of black art; yes there's a lot of how it should work on the Web, but it's correctness and viability seems to vary with the iteration of the GPU chip on the board. This is an area where experimentation & hand tuning comes into play. Usually the driver _should_ work without any "Option" setting, but I have a memory of a case where it didn't. What revision of X that was I can't recall. ============== The Second ===================== Well the "intel" driver is -supposed to cover the i915 :-? So what's no tying together? Felix talks of minimalist set of "50-" conf files. Do you have all those files? Whether its easier to debug a single "xorg.conf" file or the separate "50-" files us debatable. Personally I prefer the latter. However I do agree with Felix that stripping the files back to the very basics *AND* making sure you have them all is a necessary. Putting them all in one file is an alternative debug move. But do you actually have all those "50-" files? I'd send you my config files where I've eventually specified just about everything to customise my multibutton mouse, multifunction keyboard as well as the much hacked about monitor and device and screen files, but, as I say, they are very hacked about! -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward composed on 2016-03-22 12:43 (UTC-0400):
But do you actually have all those "50-" files?
Unless he deleted them, he has them. They're contained in http://download.opensuse.org/tumbleweed/repo/oss/suse/x86_64/xorg-x11-driver... and in all the corresponding versions for that package for 42.1, 13.2, 13.1, 12.3, 12.2 and back to 11.4, the version that was current in July 2011. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/22/2016 01:06 PM, Felix Miata wrote:
Anton Aylward composed on 2016-03-22 12:43 (UTC-0400):
But do you actually have all those "50-" files?
Unless he deleted them, he has them. They're contained in http://download.opensuse.org/tumbleweed/repo/oss/suse/x86_64/xorg-x11-driver... and in all the corresponding versions for that package for 42.1, 13.2, 13.1, 12.3, 12.2 and back to 11.4, the version that was current in July 2011.
Yes I'm aware of all that. But it never hurts to check the trivial. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward composed on 2016-03-22 13:21 (UTC-0400):
Felix Miata wrote:
Anton Aylward composed on 2016-03-22 12:43 (UTC-0400):
But do you actually have all those "50-" files?
Unless he deleted them, he has them. They're contained in http://download.opensuse.org/tumbleweed/repo/oss/suse/x86_64/xorg-x11-driver... and in all the corresponding versions for that package for 42.1, 13.2, 13.1, 12.3, 12.2 and back to 11.4, the version that was current in July 2011.
Yes I'm aware of all that. But it never hurts to check the trivial.
Thus, in my earlier reply to which you referred: Felix Miata composed on 2016-03-22 12:28 (UTC-0400): ...
For /etc/X11/xorg.d.conf/20-intel.conf to have any effect, /etc/X11/xorg.d.conf/ must contain corresponding device, monitor and screen sections, as the entirely commented July 2011 example files
50-device.conf 50-monitor.conf 50-screen.conf
in /etc/X11/xorg.d.conf/... -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
============== The First =====================
Now I have a
$ sudo /sbin/lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express Integrated Graphics Controller (rev 02)
and that uses the "intel" driver.
When your X server tries loading the "intel" driver for your GPU it fails, somehow and unloads.
(II) UnloadModule: "intel"
Thanks Anton, that's how I read that too. There doesn't seem to be any other indication of _why_ though.
That may be becuase you have one or more "Option" settings that it barfs on, but in this case I think you are wrong to use the "intel" driver.
AFAICT, there are no options specific to the driver. The only way I've managed to get this to work is to use the default xorg.conf.install.
There is a 915 driver:
find /lib -name '*915*' /lib/modules/4.5.0-3.g8ec3d36-default/kernel/drivers/gpu/drm/i915 /lib/modules/4.5.0-3.g8ec3d36-default/kernel/drivers/gpu/drm/i915/i915.ko /lib/firmware/i915 /lib/firmware/LICENSE.i915
And that firmware.
Have you tried using that?
Yep, I went all the way to KOTD 4.5 (last week).
Yes there are a lot of bugs listed for the 915 driver, but that's the case, I see, for just about every other one :-( According the bug list the driver I'm using shouldn't work with my hardware.
I've noticed that the installers (and Knoppix) seem to be able to probe and find out which driver to use quite effectively. Maybe see what they leave as 'debris files".
Well, without xorg.conf.install I had to use "nomodeset" to get anywhere. After that I ended up using xorg.conf.install which gives me a working system, just without sufficient video performance.
A word of warning. The "Option" setting is a some kind of black art; yes there's a lot of how it should work on the Web, but it's correctness and viability seems to vary with the iteration of the GPU chip on the board. This is an area where experimentation & hand tuning comes into play.
No problem, I'm already way into that. :-)
Usually the driver _should_ work without any "Option" setting, but I have a memory of a case where it didn't. What revision of X that was I can't recall.
I guess "Options" is a directive that goes into e.g. xorg.d/20-intel.conf ?
Whether its easier to debug a single "xorg.conf" file or the separate "50-" files us debatable. Personally I prefer the latter.
However I do agree with Felix that stripping the files back to the very basics *AND* making sure you have them all is a necessary. Putting them all in one file is an alternative debug move.
But do you actually have all those "50-" files?
I presume so, apart from adding 20-intel.conf, I haven't changed, added or removed anything. I'll check to see what I have. -- Per Jessen, Zürich (3.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/23/2016 03:12 AM, Per Jessen wrote:
The only way I've managed to get this to work is to use the default xorg.conf.install.
What do you mean by that? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
On 03/23/2016 03:12 AM, Per Jessen wrote:
The only way I've managed to get this to work is to use the default xorg.conf.install.
What do you mean by that?
It was suggested somewhere to copy "xorg.conf.install" to "xorg.conf" and boot with that. Anyway, I think we can ignore that, I've moved on. -- Per Jessen, Zürich (7.3°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/23/2016 03:12 AM, Per Jessen wrote:
Well, without xorg.conf.install I had to use "nomodeset" to get anywhere. After that I ended up using xorg.conf.install which gives me a working system, just without sufficient video performance.
So, you have a baseline to experiment with ...
A word of warning. The "Option" setting is a some kind of black art;
I really do mean that.
yes there's a lot of how it should work on the Web, but it's correctness and viability seems to vary with the iteration of the GPU chip on the board.
I really do mean that. I have, from the Closet of Anxieties, a bunch of SPF desktops, all of which are supposed to be the same model, same mobo. They were bought, corporately, as a batch, CC depreciated on teh corporate books as a batch, replaced and shoved in teh closet as a batch. Under the hood I find different iterations of the CPU chip and GPU chip, which is supposed to be an i915. I found that if I installed the 915 driver with some Options i could get pretty good performance. Then the machine, as machines from the Closet of Anxieties are wont to do, hmmm, hmmm, "expired", so to speak, and i moved the hard disk to the next one. it sort of like the opening scene to the old SCTV program. I call it "toilet paper computing". There's always another roll on the closet. https://www.youtube.com/user/TheOfficialSCTV But those finely tuned settings for the old video now would not work with the supposedly identical video on the new box! So, back to the "baseline" and tuning all over again. You may gather from this that the 915 is not my favourite GPU
This is an area where experimentation & hand tuning comes into play. No problem, I'm already way into that. :-)
Usually the driver _should_ work without any "Option" setting, but I have a memory of a case where it didn't. What revision of X that was I can't recall. I guess "Options" is a directive that goes into e.g. xorg.d/20-intel.conf
!WHAT!? Where did that come from? Did the installer create it or did you/ If that has a "Device" stanza than please explain why you aren't using xorg.d/50-device.conf like 'everyone else' -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
On 03/23/2016 03:12 AM, Per Jessen wrote:
Well, without xorg.conf.install I had to use "nomodeset" to get anywhere. After that I ended up using xorg.conf.install which gives me a working system, just without sufficient video performance.
So, you have a baseline to experiment with ...
Yup.
I have, from the Closet of Anxieties, a bunch of SPF desktops, all of which are supposed to be the same model, same mobo. They were bought, corporately, as a batch, CC depreciated on teh corporate books as a batch, replaced and shoved in teh closet as a batch. Under the hood I find different iterations of the CPU chip and GPU chip, which is supposed to be an i915.
I found that if I installed the 915 driver with some Options i could get pretty good performance. Then the machine, as machines from the Closet of Anxieties are wont to do, hmmm, hmmm, "expired", so to speak, and i moved the hard disk to the next one.
But those finely tuned settings for the old video now would not work with the supposedly identical video on the new box! So, back to the "baseline" and tuning all over again.
Do you have any link or hints wrt those settings? My current tv-system uses the built-in i915 which is sufficient for SDTV, but not quite for HDTV, hence the need for this upgrade. If there are options/settings for i915 that might squeeze enough out of it to run HDTV .....
You may gather from this that the 915 is not my favourite GPU
I have tried putting a modern(ish) low-profile pcie card in the current tv-system, but for some reason it refuses to boot with it.
I guess "Options" is a directive that goes into e.g. xorg.d/20-intel.conf
!WHAT!?
Where did that come from? Did the installer create it or did you/
I created that as a result of many hours of experimenting and googling.
If that has a "Device" stanza than please explain why you aren't using xorg.d/50-device.conf like 'everyone else'
Yeah, I was not aware of the 50-files being used by everybody else. -- Per Jessen, Zürich (6.8°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Anton Aylward -
Bjoern Voigt -
Felix Miata -
Freek de Kruijf -
Per Jessen