[Intel-gfx] No Mesa DRI Intel 945G in Debian Bookworm since Feb. 2022 package change
>From libgl1-mesa-dri:amd64 changelog:
mesa (22.0.0~rc2-1) experimental; urgency=medium
* New upstream release candidate.
* path_max.diff: Refreshed.
* rules: Drop classic drivers (r100, r200, nouveau_vieux, i915, i965).
-- Timo Aaltonen Thu, 17 Feb 2022 22:04:03 +0200
# xdriinfo
libGL error: MESA-LOADER: failed to open i915: /usr/lib/dri/i915_dri.so: cannot
open shared object file: No such file or directory (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
libGL error: failed to load driver: i915
Screen 0: swrast
# pinxi -GSaz --vs --zl --hostname
pinxi 3.3.23-05 (2022-11-07)
System:
Host: gx62b Kernel: 5.19.0-2-amd64 arch: x86_64 bits: 64 compiler: gcc
v: 11.3.0 parameters: root=LABEL= ipv6.disable=1 net.ifnames=0
biosdevname=0 plymouth.enable=0 noresume mitigations=auto consoleblank=0
Desktop: Trinity v: R14.0.13 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0
vt: 7 dm: 1: TDM 2: XDM Distro: Debian GNU/Linux bookworm/sid
Graphics:
Device-1: Intel 82945G/GZ Integrated Graphics vendor: Dell driver: i915
v: kernel arch: Gen-3.5 process: Intel 90nm built: 2005-06 ports:
active: DVI-D-1,VGA-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:2772
class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting
dri: swrast gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 3600x1200 s-dpi: 120 s-size: 762x254mm (30.00x10.00")
s-diag: 803mm (31.62")
Monitor-1: DVI-D-1 pos: primary,left model: NEC EA243WM serial:
built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
max: 1920x1200 min: 640x480
Monitor-2: VGA-1 pos: right model: Dell P2213 serial: built: 2012
res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65")
diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400
API: OpenGL v: 4.5 Mesa 22.2.4 renderer: llvmpipe (LLVM 15.0.5 128 bits)
direct render: Yes
In Bullseye:
...
API: OpenGL v: 1.4 Mesa 20.3.5 renderer: Mesa DRI Intel 945G
direct render: Yes
# xdriinfo
Screen 0: i915
What are Bookworm users supposed to do to make Mesa DRI work correctly
now that i915_dri.so is missing? Did it get moved to some other .deb
I can't ID? I don't think Crocus is supposed to work on Gen3. At least,
export MESA_LOADER_DRIVER_OVERRIDE=crocus in /etc/X11/Xsession.d/10-crocus.sh
doesn't help.
In openSUSE Tumbleweed in 22.2.4 i915 is still included in its Mesa-dri
package, and Mesa DRI Intel 945G is working as expected.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
Re: [Intel-gfx] KMS start locks up RocketLake-S GT1
Felix Miata composed on 2021-12-12 00:37 (UTC-0500): > Is there a command line option needed for RocketLake-S GT1 on i5-11400? Is it > supposed to use some module other than i915? Tumbleweed kernel 5.15.6 locks > up, > apparently when KMS should be kicking in. I can't get any logs or dmesg except > when booting with nomodeset. Reported: https://gitlab.freedesktop.org/drm/intel/-/issues/4762 -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
[Intel-gfx] KMS start locks up RocketLake-S GT1
Is there a command line option needed for RocketLake-S GT1 on i5-11400? Is it supposed to use some module other than i915? Tumbleweed kernel 5.15.6 locks up, apparently when KMS should be kicking in. I can't get any logs or dmesg except when booting with nomodeset. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
[Intel-gfx] i810e & i815 no /dev/dri/card0
https://manpages.debian.org/testing/xserver-xorg-video-intel/intel.4.en.html says these IGPs are supported. Is this true? I'm trying to get them to work in Debian Stretch and Buster, but having no luck finding /dev/dri/card0. What doc explains how to acquire it? VESA is producing only 640x480. :~( I see in http://bugzilla.opensuse.org/show_bug.cgi?id=1185174 it requires heroics as of kernel 5.12. :( But, Stretch is on 4.9 and Buster is on 4.19, so should still work, right? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] sad output names
Rodrigo Vivi composed on 2018-07-25 09:20 (UTC-0700): > On Wed, Jul 25, 2018 at 03:37:52AM -0400, Felix Miata wrote: >> Asus B250 LGA 1151 (Kaby Lake) Motherboard (4 total physical video outputs): >> https://www.asus.com/us/Motherboards/PRIME-B250M-C-CSM/ >> G4600 HD Graphics 630 CPU >> Server 1.20.0 (openSUSE Tumbleweed) >> kernel 4.17.4 >> Xorg driver: modesetting >> Xrandr Actual Cable >> Reports Connectors >> DP-1 DisplayPort >> HDMI-1 >> HDMI-2 HDMI >> HDMI-3 DVI >> DP-2 VGA > I understand your concern, but as you can see there are adaptors involved > here and they are decided by manufactures. From the driver perspective the > protocol is the most important part, but that gets sometimes really bad for > the users, I know. By "adaptors", do you mean logical adapters in motherboard firmware that maybe an update could improve? > Honestly I don't know if there's a way to detect the presence of adapters > like this DP to VGA for instance. I don't think so. > Afaik on HDMI-DP with LSPCON we do some tweak on the names to avoid > showing a misleading information, but that's is the further we can go I'm > afraid... Thanks for the reply. BTW, DP daisy chaining the same motherboard I get the following: Screen 0: minimum 320 x 200, current 4480 x 1200, maximum 8192 x 8192 DP-1 disconnected primary (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) HDMI-3 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-1-8 connected 2560x1080+0+0 (normal left inverted right x axis y axis) 673mm x 284mm 2560x1080 60.00*+ 1920x1080 60.0060.0050.0059.9424.0023.98 1680x1050 59.95 1280x1024 75.0260.02 1280x800 59.81 1152x864 75.00 1280x720 60.0050.0059.94 ... DP-1-1 connected 1920x1200+2560+0 (normal left inverted right x axis y axis) 519mm x 324mm 1920x1200 59.95*+ 1920x1080 60.0059.94 1680x1050 59.95 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1280x800 59.81 1280x720 60.0059.94 ... That logic looks backwards to me. DP-1-8 is the screen in the middle of the cable chain. :-p >> Is there anything with kernel, xrandr, driver, server (or other?) that might >> be >> changed to better associate the connector names to the actual connector >> types? >> Is this a motherboard firmware shortcoming?-- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] sad output names
Asus B250 LGA 1151 (Kaby Lake) Motherboard (4 total physical video outputs): https://www.asus.com/us/Motherboards/PRIME-B250M-C-CSM/ G4600 HD Graphics 630 CPU Server 1.20.0 (openSUSE Tumbleweed) kernel 4.17.4 Xorg driver: modesetting Xrandr Actual Cable Reports Connectors DP-1DisplayPort HDMI-1 HDMI-2 HDMI HDMI-3 DVI DP-2VGA Is there anything with kernel, xrandr, driver, server (or other?) that might be changed to better associate the connector names to the actual connector types? Is this a motherboard firmware shortcoming? -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] sad output names
Felix Miata composed on 2018-07-25 03:37 (UTC-0400): > Asus B250 LGA 1151 (Kaby Lake) Motherboard (4 total physical video outputs): > https://www.asus.com/us/Motherboards/PRIME-B250M-C-CSM/ > G4600 HD Graphics 630 CPU > Server 1.20.0 (openSUSE Tumbleweed) > kernel 4.17.4 > Xorg driver: modesetting > > XrandrActual Cable > Reports Connectors > DP-1 DisplayPort > HDMI-1 > HDMI-2HDMI > HDMI-3DVI > DP-2 VGA > Is there anything with kernel, xrandr, driver, server (or other?) that might > be > changed to better associate the connector names to the actual connector types? > Is this a motherboard firmware shortcoming? Meant to include this first try, in case it matters, but got sidetracked: http://fm.no-ip.com/Tmp/Linux/Xorg/Igfx/xorg.0.log-intel-gfx-listpost-ab250connectors -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] [Eaglelake][i915] pipe state doesn't match
I looked for a match on https://bugs.freedesktop.org/query.cgi but found nothing looking like a close match that hadn't been marked fixed or duplicate. This is happening on a Dell Optiplex 780 in every openSUSE boot at least as far back as kernel 3.16 in v13.2, but is not evident in v13.1 running 3.12.59. It's also evident in Knoppix 7.6.1 & kernel 4.2.6. This is full dmesg from Tumbleweed's kernel 4.6.3, vaapi-intel-driver-1.7.0 and libdrm2-2.4.68/libdrm_intel1-2.4.68, with the following cmdline: audit=0 ipv6.disable=1 net.ifnames=0 noresume splash=0 vga=791 video=1024x768@60 video=1440x900@60 3 http://fm.no-ip.com/Tmp/SUSE/Factory/dmsg-gx780-tw20160710-k4631.txt Dmesg excerpt: [ 11.571101] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in has_audio (expected 1, found 0) [ 11.571102] [ cut here ] [ 11.571128] WARNING: CPU: 0 PID: 71 at ../drivers/gpu/drm/i915/intel_display.c:12921 intel_modeset_check_state+0x6b6/0x840 [i915] [ 11.571129] pipe state doesn't match! [ 11.571149] Modules linked in: snd_hda_core snd_hwdep mei_wdt snd_pcm i915 snd_timer drm_kms_helper dm_mod snd mei_me drm e1000e fb_sys_fops mei coretemp kvm_intel kvm dell_wmi ptp sparse_keymap acpi_cpufreq dell_smbios video ppdev tpm_tis syscopyarea button iTCO_wdt tpm shpchp parport_pc gpio_ich sysfillrect dcdbas parport wmi iTCO_vendor_support sysimgblt pps_core i2c_i801 floppy(+) lpc_ich mfd_core irqbypass soundcore i2c_algo_bit 8250_fintek pcspkr hid_generic usbhid uhci_hcd ehci_pci ehci_hcd serio_raw sr_mod cdrom usbcore usb_common ata_generic sg [ 11.571151] CPU: 0 PID: 71 Comm: kworker/u16:6 Not tainted 4.6.3-1-default #1 [ 11.571152] Hardware name: Dell Inc. OptiPlex 780 /03NVJ6, BIOS A14 08/21/2012 [ 11.571155] Workqueue: events_unbound async_run_entry_fn [ 11.571157] 8138a6f4 8800d7b83988 [ 11.571158] 8107b10e 8800d4f7b800 8800d7b839d8 880112574000 [ 11.571159] 880112a00c00 8800d3734400 8800d7b24000 8107b17f [ 11.571160] Call Trace: [ 11.571168] [] dump_trace+0x5e/0x300 [ 11.571171] [] show_stack_log_lvl+0x10c/0x180 [ 11.571173] [] show_stack+0x21/0x40 [ 11.571175] [] dump_stack+0x5c/0x78 [ 11.571178] [] __warn+0xbe/0xe0 [ 11.571180] [] warn_slowpath_fmt+0x4f/0x60 [ 11.571206] [] intel_modeset_check_state+0x6b6/0x840 [i915] [ 11.571240] [] intel_atomic_commit+0x832/0xc50 [i915] [ 11.571252] [] restore_fbdev_mode+0x22c/0x260 [drm_kms_helper] [ 11.571261] [] drm_fb_helper_restore_fbdev_mode_unlocked+0x2e/0x70 [drm_kms_helper] [ 11.571267] [] drm_fb_helper_set_par+0x29/0x50 [drm_kms_helper] [ 11.571293] [] intel_fbdev_set_par+0x16/0x60 [i915] [ 11.571297] [] fbcon_init+0x563/0x5f0 [ 11.571301] [] visual_init+0xc3/0x120 [ 11.571303] [] do_bind_con_driver+0x1cf/0x3b0 [ 11.571305] [] do_take_over_console+0x14e/0x1c0 [ 11.571308] [] do_fbcon_takeover+0x58/0xb0 [ 11.571311] [] notifier_call_chain+0x45/0x70 [ 11.571313] [] __blocking_notifier_call_chain+0x41/0x60 [ 11.571315] [] register_framebuffer+0x202/0x330 [ 11.571322] [] drm_fb_helper_initial_config+0x26c/0x420 [drm_kms_helper] [ 11.571348] [] intel_fbdev_initial_config+0x1b/0x30 [i915] [ 11.571350] [] async_run_entry_fn+0x43/0x140 [ 11.571352] [] process_one_work+0x1ed/0x4b0 [ 11.571354] [] worker_thread+0x47/0x4c0 [ 11.571357] [] kthread+0xbd/0xe0 [ 11.571360] [] ret_from_fork+0x22/0x40 [ 11.572001] DWARF2 unwinder stuck at ret_from_fork+0x22/0x40 [ 11.572001] Leftover inexact backtrace: [ 11.572001] [] ? kthread_worker_fn+0x170/0x170 [ 11.572932] ---[ end trace a60da7830c1f6140 ]--- [ 11.653070] Console: switching to colour frame buffer device 180x56 -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [Eaglelake][i915] pipe state doesn't match
I suspect this might be at root in these threads: https://lists.freedesktop.org/archives/intel-gfx/2016-March/089805.html https://lists.freedesktop.org/archives/intel-gfx/2016-June/097652.html Felix Miata composed on 2016-07-15 05:43 (UTC-0400): I looked for a match on https://bugs.freedesktop.org/query.cgi but found nothing looking like a close match that hadn't been marked fixed or duplicate. This is happening on a Dell Optiplex 780 in every openSUSE boot at least as far back as kernel 3.16 in v13.2, but is not evident in v13.1 running 3.12.59. It's also evident in Knoppix 7.6.1 & kernel 4.2.6. This is full dmesg from Tumbleweed's kernel 4.6.3, vaapi-intel-driver-1.7.0 and libdrm2-2.4.68/libdrm_intel1-2.4.68, with the following cmdline: audit=0 ipv6.disable=1 net.ifnames=0 noresume splash=0 vga=791 video=1024x768@60 video=1440x900@60 3 http://fm.no-ip.com/Tmp/SUSE/Factory/dmsg-gx780-tw20160710-k4631.txt Dmesg excerpt: [ 11.571101] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in has_audio (expected 1, found 0) [ 11.571102] [ cut here ] [ 11.571128] WARNING: CPU: 0 PID: 71 at ../drivers/gpu/drm/i915/intel_display.c:12921 intel_modeset_check_state+0x6b6/0x840 [i915] [ 11.571129] pipe state doesn't match! [ 11.571149] Modules linked in: snd_hda_core snd_hwdep mei_wdt snd_pcm i915 snd_timer drm_kms_helper dm_mod snd mei_me drm e1000e fb_sys_fops mei coretemp kvm_intel kvm dell_wmi ptp sparse_keymap acpi_cpufreq dell_smbios video ppdev tpm_tis syscopyarea button iTCO_wdt tpm shpchp parport_pc gpio_ich sysfillrect dcdbas parport wmi iTCO_vendor_support sysimgblt pps_core i2c_i801 floppy(+) lpc_ich mfd_core irqbypass soundcore i2c_algo_bit 8250_fintek pcspkr hid_generic usbhid uhci_hcd ehci_pci ehci_hcd serio_raw sr_mod cdrom usbcore usb_common ata_generic sg [ 11.571151] CPU: 0 PID: 71 Comm: kworker/u16:6 Not tainted 4.6.3-1-default #1 [ 11.571152] Hardware name: Dell Inc. OptiPlex 780 /03NVJ6, BIOS A14 08/21/2012 [ 11.571155] Workqueue: events_unbound async_run_entry_fn [ 11.571157] 8138a6f4 8800d7b83988 [ 11.571158] 8107b10e 8800d4f7b800 8800d7b839d8 880112574000 [ 11.571159] 880112a00c00 8800d3734400 8800d7b24000 8107b17f [ 11.571160] Call Trace: [ 11.571168] [] dump_trace+0x5e/0x300 [ 11.571171] [] show_stack_log_lvl+0x10c/0x180 [ 11.571173] [] show_stack+0x21/0x40 [ 11.571175] [] dump_stack+0x5c/0x78 [ 11.571178] [] __warn+0xbe/0xe0 [ 11.571180] [] warn_slowpath_fmt+0x4f/0x60 [ 11.571206] [] intel_modeset_check_state+0x6b6/0x840 [i915] [ 11.571240] [] intel_atomic_commit+0x832/0xc50 [i915] [ 11.571252] [] restore_fbdev_mode+0x22c/0x260 [drm_kms_helper] [ 11.571261] [] drm_fb_helper_restore_fbdev_mode_unlocked+0x2e/0x70 [drm_kms_helper] [ 11.571267] [] drm_fb_helper_set_par+0x29/0x50 [drm_kms_helper] [ 11.571293] [] intel_fbdev_set_par+0x16/0x60 [i915] [ 11.571297] [] fbcon_init+0x563/0x5f0 [ 11.571301] [] visual_init+0xc3/0x120 [ 11.571303] [] do_bind_con_driver+0x1cf/0x3b0 [ 11.571305] [] do_take_over_console+0x14e/0x1c0 [ 11.571308] [] do_fbcon_takeover+0x58/0xb0 [ 11.571311] [] notifier_call_chain+0x45/0x70 [ 11.571313] [] __blocking_notifier_call_chain+0x41/0x60 [ 11.571315] [] register_framebuffer+0x202/0x330 [ 11.571322] [] drm_fb_helper_initial_config+0x26c/0x420 [drm_kms_helper] [ 11.571348] [] intel_fbdev_initial_config+0x1b/0x30 [i915] [ 11.571350] [] async_run_entry_fn+0x43/0x140 [ 11.571352] [] process_one_work+0x1ed/0x4b0 [ 11.571354] [] worker_thread+0x47/0x4c0 [ 11.571357] [] kthread+0xbd/0xe0 [ 11.571360] [] ret_from_fork+0x22/0x40 [ 11.572001] DWARF2 unwinder stuck at ret_from_fork+0x22/0x40 [ 11.572001] Leftover inexact backtrace: [ 11.572001] [] ? kthread_worker_fn+0x170/0x170 [ 11.572932] ---[ end trace a60da7830c1f6140 ]--- [ 11.653070] Console: switching to colour frame buffer device 180x56 -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Still trying to isolate video freezes
Chris composed on 2016-06-05 16:42 (UTC-0500): In an effort to try and figure out why the video on my Dell Optiplex 780 keeps freezing I've been advised to run the latest kernel to see if it may fix the problem. Today I installed 4.6.0-997.20160502_amd64.deb and when booting it would not finish at all. There were some statements about not loading root and also about not finding a drive Is yours a SFF model 780? Overheating can cause freezing, and small case Dells, like other compact case PCs, are particularly susceptible to overheating if allowed to accumulated dust and/or tobacco tar, particularly on CPU cooler and/or within PS. Dust collected on tar acts as an insulator, containing heat within the source components. If you're sure overheating is not your problem, run memtest86 overnight or longer. You might have failing RAM. It happens. Sometimes simply reseating RAM will help if testing produces errors, but don't count on it. I can't recall my SFF 780 ever doing as yours with any Linux kernel all the way back to 3.11.7 and up through 4.5.4, and servers 1.14.x through 1.18.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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] What's using all my DRI memory?
Adam Nielsen composed on 2016-05-28 16:59 (UTC+1000): Any suggestions with this? My system just crashed again because the Intel driver used up all 16GB of my system memory. Which Intel driver version? Which X server version? Which kernel version? Which window manager/DE? Have you tried running Memtest overnight or longer? How did you decide it's the Intel driver exhausting RAM? If using X server > 16.999, have you tried removing the Intel driver, using instead the modeset driver built into the server? -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] SkyLake
cac...@quantum-sci.com composed on 2016-04-18 19:09 (UTC-0700): I take it there's no SkyLake support on the Xen side, since that starts with kernel 4.4? Which distro and kernel are you using? Modeset driver built into Xorg doesn't work for you? "The latest xf86-video-intel driver was causing font rendering problems in emacs, and switching over to the generic driver solved that and a host of other display problems I had. It feels more performant too, which is unexpected considering that I'm using skylake graphics." https://www.reddit.com/r/archlinux/comments/4cojj9/it_is_probably_time_to_ditch_xf86videointel/ -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Updated drm-intel-testing
Daniel Vetter composed on 2016-04-11 21:45 (UTC+0200): New -testing cycle with cool stuff:... What exactly is a "testing cycle? Last Intel Xorg driver (e.g. openSUSE 42.1 released in November: xf86-video-intel; Ubuntu 16.04, due out this month: xserver-xorg-video-intel) release was, what, 19 months ago, a perpetual beta (2.99.99?)? Is the meaning of "cycle" (as opposed to actual dates involved for any particular cycle) any different for drm, Mesa or other components than for the xorg "driver"? -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Video freezes continue to plague me
Chris composed on 2016-03-15 17:43 (UTC-0500): On Tue, 2016-03-15 at 16:37 -0400, Felix Miata wrote: Chris composed on 2016-03-15 14:50 (UTC-0500): > My system is a Dell Optiplex 780. Which? Tower? Desktop? SFF? USFF? Sorry, it's a desktop > I've filed several bug reports both > with the Intel Graphics Bugzilla and the Ubuntu Launchpad pages. > Initially back when this started in 2014 every 'freeze' would result in > an error of [drm:i915_hangcheck_elapsed [i915]] *ERROR* Hangcheck timer > elapsed... render ring idle' in syslog. It would happen every few days > or so and nothing that was done would correct the problem Was ensuring heat is a non-issue also done? SFF & USFF models tend to run rather hot, so accumulated dust, and especially tobacco tar, within, especially within the power supply, can become an intermittent problem for software. Currently it's 87F outside. I have a window open directly behind the system and a fan blowing on the front of it. We're just not ready to turn the AC on yet. CPU0 is running around 116F and CPU1 109F. This whole issue of the video freezing whether it's with or without the Hangcheck error has been ongoing here on my system since 13 Sept 2014. The last time the video froze with the Hangcheck error was Jan 17 2016. Since then the video has frozen without the error on 1/21/16; 1/27/16; 2/25/16; 3/08/16; 3/11/16; and today 3/15/16 at 09:50am. I came back to the desktop at around 11am to find it frozen at 9:50. I moved the mouse, the video flickered and the clock caught up and came unfrozen. The only thing in my syslog for that time is: 09:50:07 localhost kernel: [347769.284331] [drm:drm_mode_addfb2] [FB:60] 09:50:07 localhost kernel: [347769.303256] [drm:drm_mode_addfb2] [FB:62] 09:50:07 localhost kernel: [347769.324369] [drm:drm_mode_addfb2] [FB:63] Ambient temps tolerated by humans really shouldn't matter. Excess heat inside the case is often a problem elsewhere than where temp probes lie when dust has materially accumulated. What I was really asking is, is its inside reasonably clean, including inside the PSU? In 2014 it would have been around 5 or 6 years old. Also, is the PSU fan always moving some air? Maybe it's time to give it an overnight memtest workout. Could be there's become an iffy bit in the video RAM area. I have a 780 too, and a 760, and a 745, and several 620s, but they are all SFF, and don't often get left on more than a couple of hours at a time. Video lockups I don't remember ever seeing on any of them. Gnome isn't installed on any. Kubuntu on one 620 might be 14.10, but only openSUSE 13.1, 13.2, 42.1 and Tumbleweed are on my 780. 13.2 uses kernel 3.16.7, 42.1 4.1.15, and TW (currently) 4.4.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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Video freezes continue to plague me
Chris composed on 2016-03-15 14:50 (UTC-0500): My system is a Dell Optiplex 780. Which? Tower? Desktop? SFF? USFF? I've filed several bug reports both with the Intel Graphics Bugzilla and the Ubuntu Launchpad pages. Initially back when this started in 2014 every 'freeze' would result in an error of [drm:i915_hangcheck_elapsed [i915]] *ERROR* Hangcheck timer elapsed... render ring idle' in syslog. It would happen every few days or so and nothing that was done would correct the problem Was ensuring heat is a non-issue also done? SFF & USFF models tend to run rather hot, so accumulated dust, and especially tobacco tar, within, especially within the power supply, can become an intermittent problem for software. -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] setting primary in multihead xorg.conf causes disregard of DisplaySize
Possibly some fault overlap with https://bugs.freedesktop.org/show_bug.cgi?id=90842 but this is not the same. I found no other filed bugs similar. Both DisplaySize and primary display assigned as I wish with radeon. Both DisplaySize and primary display assigned as I wish with nouveau. With Intel I must choose between having the DPI I want, or having the primary display assigned as I wish. Unlike nouveau and radeon, intel won't let me have both, at least, not using a comparable xorg.conf. I tried on two different Intel gfx machines (both 4 series, one with pair of 1920x1080, other with 1680x1050 and 1920x1080), with same failing result. I ask here before filing a bug to see it there is a workaround or some specific setup requirement that intel requires and neither radeon nor nouveau do. Xorg.0.log with DisplaySize disobeyed: http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-gx760-dualIntel-goodPrimary-badDPI Xorg.0.log with Primary disobeyed: http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-gx760-dualIntel-badPrimary-goodDPI config file as last used: http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.conf-intel-1920x1080overunder-120 configs as work with nouveau and radeon: http://fm.no-ip.com/Share/Linux/xorg.conf-radeon-vga1680x1050below-dvi1920x1080above-120 http://fm.no-ip.com/Share/Linux/xorg.conf-nouveauDualDVI-1680x1050under-1920x1080over-120 -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Information sought
Ian Bruntlett composed on 2015-12-14 13:23 (UTC): > Ian Bruntlett wrote: >> I've got a couple of third hand computers using Intel graphics (Dell >> Optiplex GX50, HP Compaq dc 7600) with graphics problems - Dell becomes >> unusable, screen is all white with black squiggles after running updates on >> Ubuntu 14.04LTS- freedesktop bug 93173, dc 7600 screen works most of the >> time but occasionally is corrupted with random horizontal lines of junk >> pixels). > Well this is disappointing. No one has responded to my request for > information. For roughly 10 years now I have been refurbishing PCs to give > to people with mental health problems, their carers or families.I am an > I.T. volunteer at Contact (http://contactmorpeth.org.uk/) - and Contact won > an award from the Queen for the project I am continuing. These days Lubuntu > Linux gets put on the PCs. Many people have been given PCs with Intel > graphics so having the graphics stack broken is going to affect a lot of > vulnerable people. I've run across many Optiplex models over the years, but the GX50 predates them all. Looking up in Google it appears to be a Pentium III. Most PCs using those predate Intel onboard graphics, among which my GX200 (but not my GX150 or GX110). If your GX50 has the 810E chipset, the Intel driver has in recent years had limited functionality and marginal performance in Linux. My GX110 has 810E. I haven't powered it up in over 7 months. It's painfully slow. I don't remember if X even works in it any more. If you really think a machine nearly 2 decades old with maximum RAM population of 0.5GB warrants refurb, I suggest you find and install in it an ATI or NVidia PCI gfxcard. The OS and X need the shared RAM the 810E video is now using. The 7600 has 945G video. I have various recent distro installations (among which Kubuntu 14.04 and above) scattered among various machines using 945G experiencing none of the trouble your bugs describe, so maybe its problem is RAM or memory controller. Have you inspected its innards for exploding or leaky electrolytic capacitors? http://en.wikipedia.org/wiki/Capacitor_plague If it has any large uF (680 or higher) OST brand caps that appear normal they may nevertheless be bad and are worth checking or replacing if you believe the machine otherwise worth salvaging. Nomodeset is a workaround that blocks use of Intel driver which causes use of a low perfomance, limited function fallback driver that will use only modes provided by the machine's video BIOS. -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Changing the screen resolution permanently
Engin FIRAT composed on 2015-09-18 20:07 (UTC+0300): > In my system there are two monitors and these monitors are fed by mirrored > displays. To get such a configuration I have created a script that > dynamically adjusts the system by using xrandr. The script is attached as > changeres.sh. Everything works well. However I've note that the system > startup time is increased by ~15 seconds and I do not want such a case. To > handle this problem, I think that I need to adjust the screen resolution > permanently with a xorg.conf file. However I cannot create one that adjusts > the monitors as expected. xorg.conf file is also attached to this post. > Details of the system: > Processor: Intel Atom E3845 > OS: Lubuntu 14.04.1 > Driver: Installed via intel-graphics-installer 1.0.7 > I have tried to create a xorg.conf file with the command X -configure, > however the created file is for only one monitors since the system uses > only the first monitor at its default configuration (ie. no xrandr setting) > Could you please help me to create a correct xorg.conf file. See if this provides enough skeleton to get you going. http://fm.no-ip.com/Share/Linux/xorg.conf-inteldual03 Note that for your needs, each Section "Monitor" in it is overkill. It should be sufficient to include in each only an identifier and a position option. For 1280x1024 displays, everything else should either be unnecessary, or auto-generate via EDID. Note too that it intentionally contains no modelines. At least 99.% of the time, the system is smart enough to auto-generate whatever modeline is applicable to the appropriate mode, so don't waste your time looking for or including any modelines unless your Commander and Operator 1280x1024 displays have already proven themselves incapable of allowing appropriate auto-generation. Note that Kubuntu has a built-in utility called kscreen that autostarts unless you explicitly override it. Were you to add KDE to your Lubuntu, you might find Kscreen overriding your custom configuration: https://bugs.kde.org/show_bug.cgi?id=317929 -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] machine lockup if startup xrandr and cmdline video= and display connection is DisplayPort
96mm 1680x1050 59.97*+ 74.89 $ xdpyinfo | egrep 'dimen|ution' dimensions:1680x1050 pixels (395x246 millimeters) resolution:108x108 dots per inch Note the lockup in above case occurs after startx exits and writes various exit messages on a normal looking vtty screen. Lockup does not occur doing same in x86_64 openSUSE Tumbleweed: # openSUSE Tumbleweed host gx780 Mesa-10.6.5-120.1.x86_64 Mesa-32bit-10.6.5-120.1.x86_64 Mesa-demo-x-8.2.0-5.1.x86_64 Mesa-libEGL1-10.6.5-120.1.x86_64 Mesa-libEGL1-32bit-10.6.5-120.1.x86_64 Mesa-libGL1-10.6.5-120.1.x86_64 Mesa-libGL1-32bit-10.6.5-120.1.x86_64 Mesa-libGLESv2-2-10.6.5-120.1.x86_64 Mesa-libglapi0-10.6.5-120.1.x86_64 Mesa-libglapi0-32bit-10.6.5-120.1.x86_64 intel-gpu-tools-1.11-1.1.x86_64 libdrm_intel1-2.4.64-1.1.x86_64 libdrm_intel1-32bit-2.4.64-1.1.x86_64 libxcb-dri2-0-1.11-3.3.x86_64 libxcb-dri2-0-32bit-1.11-3.3.x86_64 libxcb-dri3-0-1.11-3.3.x86_64 libxcb-dri3-0-32bit-1.11-3.3.x86_64 vaapi-intel-driver-1.6.0-1.1.x86_64 xf86-video-intel-2.99.917-3.1.x86_64 xorg-x11-driver-video-7.6_1-15.1.x86_64 $ grep 'using VT' /var/log/Xorg.0.log [ 3934.915] (++) using VT number 3 $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) $ grep chipsets /var/log/Xorg.0.log | egrep -v 'VESA|FBDEV' $ grep PRETTY /etc/os-release PRETTY_NAME="openSUSE 20150908 (Tumbleweed) (x86_64)" $ grep 'X.Org X Server' /var/log/Xorg.0.log X.Org X Server 1.17.2 $ grep 'Current Operating System' /var/log/Xorg.0.log [ 3934.878] Current Operating System: Linux gx780 4.1.6-1-desktop #1 SMP PREEMPT Mon Aug 17 14:43:25 UTC 2015 (9dbe563) x86_64 $ grep 'Kernel Command Line' /var/log/Xorg.0.log [ 3934.878] Kernel command line: root=LABEL=09ostw64 audit=0 ipv6.disable=1 net.ifnames=0 noresume splash=0 video=1440x900@60 3 $ grep Output /var/log/Xorg.0.log | egrep -v 'disconnec|no monit' | grep -v 'nitor sect' [ 3935.008] (--) intel(0): Output DP1 using initial mode 1440x900 on pipe 0 $ egrep -i "physical size|cm]" /var/log/Xorg.0.log [ 3935.068] (II) intel(0): Setting screen physical size to 381 x 238 $ grep -v ^\# /etc/X11/xorg.conf.d/50-monitor.conf | grep DisplaySize $ grep -v ^\# /etc/X11/xorg.conf | grep DisplaySize $ grep -v ^\# /etc/X11/xorg.conf.d/50-monitor.conf | grep PreferredMode $ grep -v ^\# /etc/X11/xorg.conf | grep PreferredMode $ grep -v ^\# /etc/X11/xinit/xinitrd.d/setup | grep xrandr xrandr --dpi 108 --output DP1 --mode 1680x1050 # intel digital $ xrdb -query | grep dpi $ xrandr | egrep 'onnect|creen|\*' | grep -v disconn | sort -r Screen 0: minimum 8 x 8, current 1680 x 1050, maximum 32767 x 32767 DP1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 296mm 1680x1050 59.97*+ 74.89 $ xdpyinfo | egrep 'dimen|ution' dimensions:1680x1050 pixels (395x246 millimeters) resolution:108x108 dots per inch Neither does the lockup occur in the 13.2 installation if the xrandr script has s/DP1/VGA1/ and the machine booted after the cable is changed from DisplayPort to standard 15 pin VGA. In amd64 Debian Jessie (kernel 3.16, server 1.16.4), lockup on exit does not occur, but there is a startx exit oops/Call Trace preceding the line "(EE) Server terminated successfully (0). Closing Log file." that does not show up in .xsession-errors or in Xorg.0.log, starting with a WARNING about check_crtc_state pipe state doesn't match. Is lockup using DisplayPort cable a known problem? Kernel? Driver? Xorg? Other? -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] panning crash
Chris Wilson composed on 2015-06-13 09:19 (UTC+0100): Thank you for responding! > On Sat, Jun 13, 2015 at 02:17:34AM -0400, Felix Miata wrote: >> Dell Optiplex GX280 >> P4 32 bit Hyperthreading enabled 0F34 2.8GHz CPU >> 00:02.0 VGA compatible controller: Intel Corporation 82915G/GV/910GL >> Integrated Graphics Controller (rev 04) >> /etc/X11/xinit/xinitrc.d/setup contains: >> xrandr --fbmm 387x218 --fb 2560x1440 --output VGA1 --mode 1920x1440 >> --panning 2560x1440 >> Panning mouse out of initial CRTC desktop space into virtual desktop space >> and back in >> some installations causes crash, in others not. Can someone here tell if >> this is a kernel, >> server or other issue and not a driver issue from a look at Xorg.0.log? My >> suspicion is >> kernel as primary if not sole. > I think the crash is in the rejection handling code. If the kernel > rejects the modeset, we try again with via a shadow. The crash is very > unexpected. You can run the stacktraces though addr2line (e.g. > addr2line -i -e /usr/lib/xorg/modules/drivers/intel_drv.so 0x638f7 > 0x68fbc 0x6a02b) Brief googling this didn't find anything I can grok. It's probably doable with minimal hand-holding, e.g. a URL explaining what tools need to be installed (gdb + ???) and how to use them. Debugging is something I do so infrequently I forget everything I managed to slog through from one session to the next. > but also compiling your own ddx with > --enable-debug=full would be very useful. Not doable. I tried programming in college over 4 decades ago. English remains as much language as I can cope with, and not even that much WRT OBS. OTOH, RPMs I can deal with. > A drm.debug=6 dmesg would tell you what is going on kernel side. Tell you maybe. :-) http://fm.no-ip.com/Tmp/Linux/Xorg/Igfx/panfault/ Fedora 21, kernel 4.0.4: dmsg-i915G-f21-k404crash.txt Tumbleweed, kernel 4.0.4: dmsg-i915G-os133-k404crash.txt Looks like maybe the crash occurred in the vicinity of [433.26] in F21, [111.57] in TW, but there's minimal sense I can make of dmesg generally. All this said, crash didn't happen in Rawhide, so maybe it's a kernel problem that has resolved itself post-4.0.4? HTH -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] panning crash
Dell Optiplex GX280 P4 32 bit Hyperthreading enabled 0F34 2.8GHz CPU 00:02.0 VGA compatible controller: Intel Corporation 82915G/GV/910GL Integrated Graphics Controller (rev 04) /etc/X11/xinit/xinitrc.d/setup contains: xrandr --fbmm 387x218 --fb 2560x1440 --output VGA1 --mode 1920x1440 --panning 2560x1440 Panning mouse out of initial CRTC desktop space into virtual desktop space and back in some installations causes crash, in others not. Can someone here tell if this is a kernel, server or other issue and not a driver issue from a look at Xorg.0.log? My suspicion is kernel as primary if not sole. Successes: Rawhide, kernel 4.1.0-0.rc7, driver 2.99.917, server 1.17.1, KDE5 Mageia 5, kernel 3.19.8, driver 2.99.917, server 1.16.4, KDE4 openSUSE 13.1, kernel 3.12.39, driver 2.99.917, server 1.15.99.903, KDE3 openSUSE 13.2, kernel 3.16.7, driver 2.99.917, server 1.17.1, KDE3 Failures: Fedora 21, kernel 4.0.4, driver 2.99.916, server 1.16.3, KDE4 Tumbleweed, kernel 4.0.4, driver 2.99.917, server 1.17.1, KDE3 Skipped testing due to unrelated issue (refuses mode 1920x1440 that xrandr claims available, uses 1600x1200 instead, and no crashing): Fedora 22, kernel 4.0.5, driver 2.99.917, server 1.17.1, KDE5 Logs: http://fm.no-ip.com/Tmp/Linux/Xorg/Igfx/panfault/ -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] EDID problem
Engin Firat composed on 2015-05-24 22:54 (UTC+0300): > I want to use custom EDID for one of my monitors. This because the monitor > has a broken EDID structure. I have been trying to use a custom EDID (a > binary message was saved before) within Xorg.conf. Is this possible? Xorg is usually smart enough to automatically produce an appropriate modeline if you simply use xorg.conf to provide the resolution you want and your diplay's HorizSync and VertRefresh specifications. IOW, manufacturing a valid EDID is usually a lot of unnecessary work. Here, it has never been a necessary workaround to oft-encountered invalid EDID. -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Lenovo X60 with i945: Setting resolution in GRUB to 1024×768
Paul Menzel composed on 2015-01-19 00:01 (UTC+0100): > Am Sonntag, den 18.01.2015, 16:56 -0500 schrieb Felix Miata: >> Paul Menzel composed on 2015-01-18 12:20 (UTC+0100): >> > Unfortunately that does not have an effect and the >> > resolution is only 640aÃ480. >> IIRC, I've solved this problem in the distant past by in BIOS setup changing >> memory size reserved for video controller from 1M to 8M. > Unfortunately I was unable to find such a configuration option in the > BIOS menu. I just rebooted a Grub Legacy/openSUSE i915 system after changing its BIOS video setting from 8M to 1M. Grub with gfxboot starts in 640x480 mode instead of 800x600, and the combination of vga=791 and video=1024x768@60 on cmdline generates an unsupported BIOS mode message from vga=791. Trying again leaving off vga=791, Grub again appears in 640x480, and boot proceeds in that mode until the kernel switches framebuffer to 1024x768. Restoring BIOS to 8M restores 1024x768 normalcy here. It appears that Grub dev is right about your BIOS; 1024x768 is not available until after the BIOS releases control, and probably until Grub2 turns the screen over to the kernel. IOW, your BIOS is your problem. -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Lenovo X60 with i945: Setting resolution in GRUB to 1024×768
Paul Menzel composed on 2015-01-18 12:20 (UTC+0100): > on the Lenovo X60 with i945 graphics (and vendor BIOS), for using > fastboot, that means to avoid a modeset, I want to set the desired > resolution in GRUB using the option `GRUB_GFXMODE=1024x768` in > `/etc/default/grub`. Making a change in /etc/default/grub does not take effect until the actual Grub menu is rebuilt. It's a config file, not a menu file. > Unfortunately that does not have an effect and the > resolution is only 640Ã480. IIRC, I've solved this problem in the distant past by in BIOS setup changing memory size reserved for video controller from 1M to 8M. > The GRUB developer told me that this is likely a Video BIOS issue. > Am I out of luck or do you know of possible solutions or do you have > pointers how to debug this? GRUBâs `vbeinfo` lists the resolution of > 1024Ã768. GRUB_GFXMODE=1024x768 assumes you are using Grub2. In Grub legacy what you need is video=1024x768 or video=1024x768@60 on the kernel cmdline. I have multiple i945G systems using both vga=1024x768@60 and Grub Legacy, but none Lenovo. Which distro are you using? -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] new behaviors: ?2.99.917?
Chris Wilson composed on 2014-12-24 07:07 (UTC): > On Wed, Dec 24, 2014 at 12:22:38AM -0500, Felix Miata wrote: >> 4 series onboard video rev 03 (G41) >> using DVI to HDMI cable on DVI motherboard connector, which Xorg reports as >> HDMI1 >> Display is 1920x1080 LCD TV, using HDMI connector #4 >> Rawhide >> kernel 3.18.1 >> Xorg 1.16.3RC1 >> xorg-x11-drv-intel-2.99.917 >> 1-connected and unconnected absent from Xorg.0.log > That's not in any -intel. You are misinterpreting verbiage in the > logfile if you think that is what 2.21.15 says. Methinks you misinterpreted my comment at the time you replied. Sometime after v2.20.19 the string "connected" disappeared from Xorg.0.log files, while remaining all along in logs created using radeon and nouveau drivers. Since your reply, Rawhide's driver moved from v2.99.917-1 to v2.99.917-2, and the string returned to the logs. >> 2-EDID preferred absent from Xorg.0.log > That's not used by any -intel. I see "First detailed timing is preferred mode" in logs generated using radeon and nouveau, and those generated using intel thru v2.20.19 and in v2.99.917-2, so absence from logs generated in the interim using intel makes me wonder why. Maybe only Xorg rather than driver is what uses it, but the difference when looking at files only from the interim period when they were absent made this the more logical place to ask. >> 3-EDID preferred is not used by Xorg > Indeed. So if -intel does not and Xorg does not, what does? >> 4-video= on cmdline if present and valid is used by Xorg instead of EDID >> preferred > Xorg inherits the current mode. This is a primary reason for the OP, a distinctly different behavior from using radeon and nouveau. I can understand the logic in it, but will be bothered by it as long as the difference among drivers remains, and would really rather it never happen that the others change to do the same as what intel started doing . It's a long tradition that the kernel cmdline options affecting framebuffer vtys (vga= pre-KMS, video= using KMS) not be inherited by Xorg. Those have quickly and easily at boot time enabled the vty rows and columns to be indirectly adjusted to provide a comfortable text size without impacting the much more elaborately configured X desktops. Current intel behavior requires an additional Xorg 'Section "Device"' option to get the configured DisplaySize onto the default output in place of the automagic that worked not so long ago in intel, and still can in radeon and nouveau. Logs supporting my comments: http://fm.no-ip.com/Tmp/Linux/Xorg/Igfx/ -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] new behaviors: ?2.99.917?
4 series onboard video rev 03 (G41) using DVI to HDMI cable on DVI motherboard connector, which Xorg reports as HDMI1 Display is 1920x1080 LCD TV, using HDMI connector #4 Rawhide kernel 3.18.1 Xorg 1.16.3RC1 xorg-x11-drv-intel-2.99.917 1-connected and unconnected absent from Xorg.0.log 2-EDID preferred absent from Xorg.0.log 3-EDID preferred is not used by Xorg 4-video= on cmdline if present and valid is used by Xorg instead of EDID preferred Are each or any of these now expected? None occur in F20, kernel 3.17.7, server 1.14.3, driver 2.21.15. http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-f22-i299917drv-1024x768-brokenAutoMagic -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Fast User Switching does not seem to work
constantine composed on 2014-10-09 13:35 (UTC): >> Does your Arch use systemd? >> Is your *buntu not using systemd? > Yes to both. > I am aware of the on-demand "feature" and did what you proposed (had > already done the same for half of the terminals). > After testing I noticed something more specific. > Suppose the following tty2,3 or VT: > 1. Ctrl+Alt+F2:logged in user in console (no X) > 2. Ctrl+Alt+F3:logged in user in console (no X) > 3. Ctrl+Alt+F4:logged in user in Desktop Environment (X) > 4. Ctrl+Alt+F5:logged in user in Desktop Environment (X) >>From 1 to 2, or 2 to 1 there is no delay. >>From 1,2 to 3, or 1,2 to 4 there is **no** delay. >>From 3,4 to 1,2 there **is** delay. >>From 3 to 4, or 4 to 3, there **is**delay. > Do you think I should post to systemd for this? I guess any of the following could be better than here: user-mode-linux-user systemd-devel x...@freedesktop.org arch-general -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Fast User Switching does not seem to work
constantine composed on 2014-10-09 00:38 (UTC): > I am encountering a peculiar problem with Fast User Switching or Kernel > Mode Setting and I do not know how to troubleshoot it. > When I run two (or more) Virtual Terminals switching between them > (Ctrl+Alt+F2-3, etc.) takes 2+ seconds. (That is either simply initiated > with startx from tty2 and tty3 or as different displays with KDisplay > Manager (kdm) in :0 and :1) > I am using an intel graphics driver so I suppose KMS should be enabled by > default and this seems to be the case, but there still are delays swithing > VTs. > I have followed the instructions at > http://carlosbecker.com/posts/how-to-enable-kms-on-i915-graphiccard-archlinux/ > https://wiki.archlinux.org/index.php/kernel_mode_setting > https://wiki.archlinux.org/index.php/Intel_graphics but I am still > experiencing the problem. > Last, I am certain it is not a hardware related issue, because I can fast > switch in ubuntu, but not in Arch linux. > Any ideas? Does your Arch use systemd? Is your *buntu not using systemd? Distros using systemd typically configure ttys to be on demand. Others do not. I find when I do not reconfigure my systemd installations to start logins on ttys at boot, delays getting to them are normal, and annoying. IOW, I don't think your annoyance has anything to do with KMS or video driver. I do the reconfiguration on systemd installations via script, which may need to be adjusted according to whether /lib or /usr/lib is applicable to your installation: cp -a /usr/lib/systemd/system/getty@.service /usr/lib/systemd/system/getty@tty1.service sed -i 's/TTYVTDisallocate=yes/TTYVTDisallocate=no/' /usr/lib/systemd/system/getty@tty1.service ln -sf /usr/lib/systemd/system/getty@tty1.service /etc/systemd/system/getty.target.wants/getty@tty1.service systemctl start getty@tty1.service ln -sf /usr/lib/systemd/system/getty@.service /etc/systemd/system/getty.target.wants/getty@tty2.service systemctl start getty@tty2.service ln -sf /usr/lib/systemd/system/getty@.service /etc/systemd/system/getty.target.wants/getty@tty3.service systemctl start getty@tty3.service ln -sf /usr/lib/systemd/system/getty@.service /etc/systemd/system/getty.target.wants/getty@tty4.service systemctl start getty@tty4.service ln -sf /usr/lib/systemd/system/getty@.service /etc/systemd/system/getty.target.wants/getty@tty5.service systemctl start getty@tty5.service ln -sf /usr/lib/systemd/system/getty@.service /etc/systemd/system/getty.target.wants/getty@tty6.service systemctl start getty@tty6.service -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] startx on Fedora died today
On 2014-07-11 07:22 (GMT+0100) Chris Wilson composed: On Thu, Jul 10, 2014 at 09:09:31PM -0400, Felix Miata wrote: F21 branched off Rawhide over recent hours. On i945G host gx62b I cloned first, then upgraded one to current F21 state and the other to Rawhide. Before today's upgrade, which moved server from 1.15.99.903 to 1.15.99.904 on both, and kernel from rc4git0.1 to rc4git2.1, booting first to multi-user, startx was working normally. Now it won't[1], though X (KDM/KDE) does work by booting to graphical instead of multi-user[2]. Is this an already known driver problem? Server? Kernel? The difference being when it crashed it tried to open the logind fd. This is a server bug - it looks like the recent non-pci platform device conflicts with the systemd integration. Thanks. [1] http://fm.no-ip.com/Tmp/Linux/F/Xorg.0.log-fc21-3 [2] http://fm.no-ip.com/Tmp/Linux/F/Xorg.0.log-fc21-5 https://bugzilla.redhat.com/show_bug.cgi?id=1118540 already filed some hours before I found this, and happening with rv200 Radeon as well as Intel. I don't find anything related filed yet on bugs.freedesktop.org/ -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] startx on Fedora died today
F21 branched off Rawhide over recent hours. On i945G host gx62b I cloned first, then upgraded one to current F21 state and the other to Rawhide. Before today's upgrade, which moved server from 1.15.99.903 to 1.15.99.904 on both, and kernel from rc4git0.1 to rc4git2.1, booting first to multi-user, startx was working normally. Now it won't[1], though X (KDM/KDE) does work by booting to graphical instead of multi-user[2]. Is this an already known driver problem? Server? Kernel? [1] http://fm.no-ip.com/Tmp/Linux/F/Xorg.0.log-fc21-3 [2] http://fm.no-ip.com/Tmp/Linux/F/Xorg.0.log-fc21-5 -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] 3.14 issue with i810 graphic card bisected
On 2014-04-19 22:19 (GMT-0400) Felix Miata composed: Has no one opened a freedesktop.org bug for this? I couldn't find one for i810 changed more recently than 18 months ago. I have an openSUSE i810E rev03 test system with 1.16.0 RC 2. Newest changelog entry 08 April. Last intel driver 2.99.911.1-123.4 changelog entry 02 April. OK with 3.11 kernel http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-201419xorgx11-kern311OK Bad with 3.14 kernel http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-xorgx11-20140419-kern314BAD Bad also with 3.14.3 openSUSE kernel, but working with 3.15.rc5. Is the fix produced as a result of the bisection going to make it into 3.14 kernels? -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] 82845G/GL[Brookdale-G]/GE support for more resolution and external display
On 2014-05-09 16:25 (GMT-0400) Brandon composed: I have an old laptop with on board 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03) which only has 640x480 available using the xf86-video-intel v2.99.911 driver with xorg-server 1.15.1. Â Additionally, I cannot use an external monitor attached to the onboard VGA out which I know is good since I can use it under another OS. Â Is this old chipset still supported? The 845G has consistently been a thorn in developers and users' sides since new, but it still works here in post-14.x versions from Fedora, Mandriva and openSUSE at least. Here's a log from a freshly updated Rawhide system on a 1600x1200 CRT: http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-gx260-i845G-fc21-1405 Note that it's not from a laptop, so only has one real video output. And, it is configured via xorg.conf, not automagic. -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] intel(0): switch to mode spamming Xorg.0.log?
http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-intel30git has a lot of intel(0): switch to mode in sequence. Is this normal/expected behavior? Known bug? -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] 3.14 issue with i810 graphic card bisected
Has no one opened a freedesktop.org bug for this? I couldn't find one for i810 changed more recently than 18 months ago. I have an openSUSE i810E rev03 test system with 1.16.0 RC 2. Newest changelog entry 08 April. Last intel driver 2.99.911.1-123.4 changelog entry 02 April. OK with 3.11 kernel http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-201419xorgx11-kern311OK Bad with 3.14 kernel http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-xorgx11-20140419-kern314BAD -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Eyestrain problems with new Intel drivers
On 2014-03-31 10:05 (GMT+0200) Janus composed: I have the same problem as the one described by Michael bellow: the Intel Graphic card produces eye strain and headache after some minutes of using it. I found a lot of people complaining on the same problem, but no solution. I tried lowering the resolution, increasing the PWM frequency, but without luck. I also installed an old version of intel drivers (2.20.12), because the subject of this email was "with **new** Intel drivers", but it didn't help. I have a new HP Folio 9470m, with the Intel HD 4000 graphic card, and I cannot use it. Even when connecting an external monitor, I have the same problem. When I connect my old laptop, with an nvidia card, to the same monitor, the eyestrain disapear, so it must be the Intel card, or its driver. I will be glad to provide any information you consider relevant. I can do whatever test you want, but please, do not ignore this message. I am not the only one to have this problem: https://www.google.com/search?q=Eye+strain+Intel+graphic I am on (Arch) Linux, but I saw some reports on Windows too. What is output from 'lspci | grep VGA'? Exactly what model is your external display? Does disabling compositing help? Is it better if you boot a Live Linux media from a year or two or three ago, e.g. Knoppix 7.0.5 or openSUSE 12.3 or Mageia 2 or Fedora 18? On Mon, Jan 9, 2014 at 3:30 PM, Michael Vanier wrote: http://lists.freedesktop.org/archives/intel-gfx/2014-January/038104.html -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] where are docs for VIRTUAL?
I see VIRTUAL1 disconnected in Xorg.0.log, several bugs filed at freedesktop.org, an announcement of 2.99.901 at http://lists.freedesktop.org/archives/xorg/2013-September/055988.html and Google hits on cgit.freedesktop.org/xorg/driver/xf86-video-intel containing strings intel-virtual-output and/or intel-virtual-overlay, but after hours trying I don't seem to be able to spot any documentation about what *exactly* intel-virtual-output is or is supposed to be capable of. intel-virtual-output in 1.15.0 and 2.99.910 on openSUSE 13.2 produces command not found. Conspicuously absent from searching opensuse.org are both intel-virtual-output and VIRTUAL1. 1-where are the docs? 2-can it replace the missing release fix for https://bugs.freedesktop.org/show_bug.cgi?id=39949 3-if yes, is it supported on i865/i915/i945 hardware? -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] i810 forgets configured rows & columns on ttys on startx shutdown
On 2013-10-29 19:19 (GMT-0400) Felix Miata composed: On 2013-10-29 13:54 (GMT+0100) Daniel Vetter composed: Userspace modesetting is known to be racy and broken, so people don't really want to waste time on digging into bugs which are most likely flukes. But if you can bisect this issue to a specific patch a fix should be possible. Again I got no clear answer to the question asked, so I guess now it's fair to assume this must be the right place for discussion after all. I've installed openSUSE 12.3. Its 3.7.10-1.16-default and server 1.13.2 behave nicely. Beyond installing Mageia 3 to get 3.8.13 and 1.13.4, and as one who does not build software even via proxy, I'm open to suggestions how to get kernels and/or other xorg versions needed to perform bisection. This problem is differently present with Mageia 3's desktop kernel 3.8.13.4. The ttys are left usable on startx exit, but the exit log X prints to screen is scrambled from mismatch between character size and line length. I don't know whether to try older kernels, or newer, even if I knew where to find any. -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] i810 forgets configured rows & columns on ttys on startx shutdown
On 2013-10-29 13:54 (GMT+0100) Daniel Vetter composed: Felix Miata wrote: On 2013-10-29 09:51 (GMT+0100) Daniel Vetter composed: >Felix Miata wrote: >>Pre-KMS it used to be that common vga= modes were useless, so I took to >>using 0x121 to escape from 80x25 screens. Using 0x8121 required specifying >>an appropriate font via config file. Even after KMS began, vga=0x8121 >>continued to work, and still does at least through kernel 3.4.47. >This is still pre-kms, there's no kms driver for i810 chipsets. So >whatever bug there is might be just bad luck or the userspace X driver >not restoring stuff correctly. But I'm pretty sure it's not a kernel >bug, at least no in the i810 driver. I was hoping for a (what appears to be a "not our bug") response that was more helpful WRT whose bug it likely is. To me it's clearly a bug report that either can be found or needs to be made at bugs.freedesktop.org, but in what component? https://bugs.freedesktop.org/describecomponents.cgi?product=xorg has a long list, among which there is only one that includes the string intel, Driver/intel, which is what this list seems to be about. Does it look like Server/General, Server/DDX/Xorg, or something else? As it manifest in more than one distro, it surely isn't likely to be downstream. Userspace modesetting is known to be racy and broken, so people don't really want to waste time on digging into bugs which are most likely flukes. But if you can bisect this issue to a specific patch a fix should be possible. Again I got no clear answer to the question asked, so I guess now it's fair to assume this must be the right place for discussion after all. I've installed openSUSE 12.3. Its 3.7.10-1.16-default and server 1.13.2 behave nicely. Beyond installing Mageia 3 to get 3.8.13 and 1.13.4, and as one who does not build software even via proxy, I'm open to suggestions how to get kernels and/or other xorg versions needed to perform bisection. -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] i810 forgets configured rows & columns on ttys on startx shutdown
On 2013-10-29 09:51 (GMT+0100) Daniel Vetter composed: Felix Miata wrote: Pre-KMS it used to be that common vga= modes were useless, so I took to using 0x121 to escape from 80x25 screens. Using 0x8121 required specifying an appropriate font via config file. Even after KMS began, vga=0x8121 continued to work, and still does at least through kernel 3.4.47. This is still pre-kms, there's no kms driver for i810 chipsets. So whatever bug there is might be just bad luck or the userspace X driver not restoring stuff correctly. But I'm pretty sure it's not a kernel bug, at least no in the i810 driver. I was hoping for a (what appears to be a "not our bug") response that was more helpful WRT whose bug it likely is. To me it's clearly a bug report that either can be found or needs to be made at bugs.freedesktop.org, but in what component? https://bugs.freedesktop.org/describecomponents.cgi?product=xorg has a long list, among which there is only one that includes the string intel, Driver/intel, which is what this list seems to be about. Does it look like Server/General, Server/DDX/Xorg, or something else? As it manifest in more than one distro, it surely isn't likely to be downstream. -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] i810 forgets configured rows & columns on ttys on startx shutdown
Embedded Dell motherboard/video BIOS has very limited VESA support!!! (F00:80x25=VGA, F01:80x50=VGA, F02:80x43=VGA, F03:80x28=VGA, F05:80x30=VGA, F07:80x60=VGA, 309:132x25=VESA, 30A:132x43=VESA, 30B:132x50=VESA, 30C:132x60=VESA, (8)120:132x25=BIOS, (8)121:132x43=BIOS, (8)122:132x50=BIOS, (8)123:132x60=BIOS) Pre-KMS it used to be that common vga= modes were useless, so I took to using 0x121 to escape from 80x25 screens. Using 0x8121 required specifying an appropriate font via config file. Even after KMS began, vga=0x8121 continued to work, and still does at least through kernel 3.4.47. Now with kernel 3.11.x (openSUSE 13.1) and 3.12.rc6 (Mageia 4): boot: ttys OK, whatever font, rows and columns kernel determines unless specified otherwise on cmdline via vga=. video= and resolution= on cmdline have no effect. Vga= still works too if font is correctly specified by config file, but only for 0x12# BIOS modes. After startx is started, before being stopped, ttys remain functional. Once startx is stopped, ttys may or may not remain functional. Sometimes after startx has been run exactly once since booting they continue to be useful. Other times, the rows and columns are no longer remembered, switching to fonts appropriate to an 80x25 screen, but outputting more than 80 columns and 25 rows, scrambling the output in part via line breaks absent when needed at column 80. -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] 845G - call trace every boot
On 2013-10-11 13:00 (GMT+0300) Ville Syrjälä composed: On Fri, Oct 11, 2013 at 12:24:04AM -0400, Felix Miata wrote: Are these happening to everyone using recent kernels and 845G? openSUSE only? 2013-10-11T00:05:50.929822-04:00 gx260 kernel: [2.621885] [ cut here ] WARNING: CPU: 0 PID: 107 at /home/abuild/rpmbuild/BUILD/kernel-desktop-3.11.3/linux-3.11/drivers/gpu/drm/i915/intel_display.c:1074 assert_pipe+0x80/0xe0 [i915]() pipe A assertion failure (expected on, current off) Already fixed: commit 67c72a12254101d4e8d9b9f3a02646ba0be84a2d Author: Daniel Vetter Date: Tue Sep 24 11:46:14 2013 +0200 drm/i915: preserve pipe A quirk in i9xx_set_pipeconf and commit a4945f9522d27e1e6d64a02ad055e83768cb0896 Author: Chris Wilson Date: Tue Oct 8 11:16:59 2013 +0100 drm/i915: Undo the PIPEA quirk for i845 Where do these show up in some bug tracker? Kernel? Freedesktop? Other? What bug #? -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] 845G - call trace every boot
Are these happening to everyone using recent kernels and 845G? openSUSE only? 2013-10-11T00:05:50.929822-04:00 gx260 kernel: [2.621885] [ cut here ] WARNING: CPU: 0 PID: 107 at /home/abuild/rpmbuild/BUILD/kernel-desktop-3.11.3/linux-3.11/drivers/gpu/drm/i915/intel_display.c:1074 assert_pipe+0x80/0xe0 [i915]() pipe A assertion failure (expected on, current off) Modules linked in: i915(+) drm_kms_helper drm i2c_algo_bit video button processor thermal_sys scsi_dh_rdac scsi_dh_emc scsi_dh_hp_sw scsi_dh_alua scsi_dh ata_generic ata_piix CPU: 0 PID: 107 Comm: udevd Not tainted 3.11.3-1-desktop #1 Hardware name: Dell Computer Corporation OptiPlex GX260 /00T606, BIOS A09 11/01/2004 0009 c071f83b f5ff3858 c02439be f8189fb8 f5ff3870 006b f8188d5c 0432 f8146820 f8146820 f6cb8000 0041 c0243a13 0009 f5ff3858 f8189fb8 f5ff3870 f8146820 f8188d5c 0432 f8189fb8 Call Trace: [] try_stack_unwind+0x179/0x190 [] dump_trace+0x47/0xf0 [] show_trace_log_lvl+0x3f/0x50 [] show_stack_log_lvl+0x50/0xd0 [] show_stack+0x1f/0x40 [] dump_stack+0x48/0x76 [] warn_slowpath_common+0x7e/0xa0 [] warn_slowpath_fmt+0x33/0x40 [] assert_pipe+0x80/0xe0 [i915] [] intel_enable_pll+0xe/0xc0 [i915] [] i9xx_crtc_enable+0x5e/0x220 [i915] [] __intel_set_mode+0x684/0x7a0 [i915] [] intel_set_mode+0x1d/0x40 [i915] [] intel_crtc_set_config+0x700/0x8f0 [i915] [] drm_mode_set_config_internal+0x43/0xb0 [drm] [] drm_fb_helper_set_par+0x45/0xb0 [drm_kms_helper] [] fbcon_init+0x482/0x4d0 [] visual_init+0x96/0xf0 [] do_bind_con_driver+0x104/0x2d0 [] do_take_over_console+0xf6/0x190 [] do_fbcon_takeover+0x57/0xc0 [] notifier_call_chain+0x46/0x60 [] __blocking_notifier_call_chain+0x37/0x50 [] blocking_notifier_call_chain+0x17/0x20 [] register_framebuffer+0x1b0/0x2d0 [] drm_fb_helper_initial_config+0x2e5/0x490 [drm_kms_helper] [] i915_driver_load+0xe8b/0xeb0 [i915] [] drm_get_pci_dev+0x129/0x230 [drm] [] local_pci_probe+0x25/0x50 [] pci_device_probe+0xcf/0xe0 [] driver_probe_device+0x74/0x360 [] __driver_attach+0x71/0x80 [] bus_for_each_dev+0x3f/0x70 [] driver_attach+0x16/0x20 [] bus_add_driver+0x1bf/0x280 [] driver_register+0x63/0x120 [] do_one_initcall+0xca/0x190 [] load_module+0x1d57/0x23f0 [] SyS_finit_module+0x75/0xc0 [] syscall_call+0x7/0xb [] 0xb7665651 ---[ end trace bd350d42e330e14d ]--- glamor-0.5.1-39.2.i586 intel-gpu-tools-1.3-20.10.i586 libdrm2-2.4.46-121.1.i586 libdrm_intel1-2.4.46-121.1.i586 vaapi-intel-driver-1.2.0-22.8.i586 x11-tools-0.1-195.1.2.noarch x11perf-1.5.4-7.17.i586 xf86-video-intel-2.99.904-89.1.i586 xorg-x11-7.6_1-183.1.noarch xorg-x11-server-7.6_1.14.3-251.17.i586 cmdline: ipv6.disable=1 noresume splash=verbose CPUFREQ=off video=1152x864@85 vga=794 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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] i810 only partially usable
On 2013-10-08 00:06 (GMT-0400) Felix Miata composed:
Still broken:
Linux gx110 3.11.3-3.gac1d7be-default #1 SMP Fri Oct 4 12:14:40 UTC 2013
(ac1d7be) i686 i686 i386 GNU/Linux
glamor-0.5.1-39.2.i586
intel-gpu-tools-1.3-20.10.i586
libdrm_intel1-2.4.46-121.1.i586
libdrm2-2.4.46-121.1.i586
vaapi-intel-driver-1.2.0-22.8.i586
xf86-video-intel-2.99.903-88.2.i586
xorg-x11-server-7.6_1.14.3-251.15.i586
Linux gx110 3.11.4-1.g40d7ca3-default #1 SMP Sat Oct 5 16:59:29 UTC 2013
(40d7ca3) i686 i686 i386 GNU/Linux
Turns out configuring a screen section in the old pre-KMS format enumerating
desired/selectable modes solves the problem, even enabling virtal (aka KMS
panning). However on exit from the X session back to the ttys, the default
mode set on boot (neither vga= nor video= on {Grub Legacy} cmdline), or one
that was set via vga= (video= is ignored), may or may not restored. When not,
the ttys are left unusable from mismatch between font used and (no longer
correct) rows/columns. Apparently the first X session following boot exits
OK, but not a second.
--
"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/
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] i810 only partially usable
On 2013-10-04 19:32 (GMT-0400) Felix Miata composed: Valid modes are now being recognized, but PreferredMode is still being ignored, and EDID preferred is inescapable via /etc/X11/xorg.conf*. Linux gx110 3.11.2-1.g420e19b-default #1 SMP Sat Sep 28 16:00:10 UTC 2013 (420e19b) i686 i686 i386 GNU/Linux glamor-0.5.1-39.1.i586 intel-gpu-tools-1.3-20.10.i586 libdrm2-2.4.46-121.1.i586 libdrm_intel1-2.4.46-121.1.i586 (no Plymouth) vaapi-intel-driver-1.2.0-22.8.i586 xf86-video-intel-2.99.903-88.2.i586 xorg-x11-server-7.6_1.14.3-251.12.i586 log: http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log.gx110-os131b1-PreferredModeIGNORED Still broken: Linux gx110 3.11.3-3.gac1d7be-default #1 SMP Fri Oct 4 12:14:40 UTC 2013 (ac1d7be) i686 i686 i386 GNU/Linux glamor-0.5.1-39.2.i586 intel-gpu-tools-1.3-20.10.i586 libdrm_intel1-2.4.46-121.1.i586 libdrm2-2.4.46-121.1.i586 vaapi-intel-driver-1.2.0-22.8.i586 xf86-video-intel-2.99.903-88.2.i586 xorg-x11-server-7.6_1.14.3-251.15.i586 -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] i810 only partially usable
On 2013-09-22 20:45 (GMT-0400) Felix Miata composed: * Awful (openSUSE 13.1 Beta 1): glamor-0.5.1-1.1 intel-gpu-tools-1.3-4.4 kernel-desktop-3.11.1-1 libdrm2-2.4.46-2.1 libdrm-intel1-2.4.46-2.1 (no Plymouth) xf86-video-intel-2.99.902-1.1 xorg-x11-server-7.6_1.14.3-1.1 (server 1.14.3) PreferredMode is apparently ignored. highest (& initial) video mode available according to xrandr and krandrtray: 1280x1024 vttys are stable only as long as X never started, regardless whether video= and/or vga= are present on cmdline. Only way I've found so far to make them work reliably again once X is started is to reboot. With various combinations of X running or not and video= and/or vga= used, vttys get scrambled in various ways (font mismatched to row and/or column counts of active mode). While X is running but a vtty is active, X/KDE3 may abort spontaneously. http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log.gx110-os131b1-0vga0video-1280x1024maxBAD http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log.gx110-os131b1-1vga1video-1280x1024maxBAD I was unable to find a bug matching this behavior on https://bugs.freedesktop.org/. Comments? Valid modes are now being recognized, but PreferredMode is still being ignored, and EDID preferred is inescapable via /etc/X11/xorg.conf*. Linux gx110 3.11.2-1.g420e19b-default #1 SMP Sat Sep 28 16:00:10 UTC 2013 (420e19b) i686 i686 i386 GNU/Linux glamor-0.5.1-39.1.i586 intel-gpu-tools-1.3-20.10.i586 libdrm2-2.4.46-121.1.i586 libdrm_intel1-2.4.46-121.1.i586 (no Plymouth) vaapi-intel-driver-1.2.0-22.8.i586 xf86-video-intel-2.99.903-88.2.i586 xorg-x11-server-7.6_1.14.3-251.12.i586 log: http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log.gx110-os131b1-PreferredModeIGNORED -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] i810 only partially usable
On 2013-09-24 11:07 (GMT+0200) Daniel Vetter composed: usually downloading the sources, patching them and rebuilding a custom rpm isn't too onerous a journey. Here, it is onerous, for multiple reasons. I tried it in 2006/2007. It isn't likely to happen again here, ever. -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] xorg.conf* screen resolution via PreferredMode disregarded by X if valid video= on cmdline
On 2013-09-23 19:41 (GMT+0100) Chris Wilson composed: On Mon, Sep 23, 2013 at 02:18:17PM -0400, Felix Miata wrote: https://bugzilla.novell.com/show_bug.cgi?id=841696 I've not had a chance to see if this also applies to Fedora and/or Mageia, or been able to tell whether it's an Intel bug rather than a Xorg bug. Maybe someone here already knows? That's an SNA bug. I thought M_T_USERPREF modes were already on the output during initial probing, however that is not the case. Again you were a bit too cryptic for my understanding. Did I again just bring to your attention a problem you hadn't been aware of but now have in queue for a fix? -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] xorg.conf* screen resolution via PreferredMode disregarded by X if valid video= on cmdline
https://bugzilla.novell.com/show_bug.cgi?id=841696 I've not had a chance to see if this also applies to Fedora and/or Mageia, or been able to tell whether it's an Intel bug rather than a Xorg bug. Maybe someone here already knows? -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] i810 only partially usable
On 2013-09-23 15:51 (GMT+0100) Chris Wilson composed: On Mon, Sep 23, 2013 at 10:13:02AM -0400, Felix Miata wrote: Did Adam already fix this? Will you be including this among your next submits? Do I need to file a bug first? You have reported the bug, I've sent the patch onwards. It would be most useful if you could test it, but I'm optimistic that Adam would be able to review it without. :-) ...I just test what others package, and get frustrated by comments like this one: https://bugs.freedesktop.org/show_bug.cgi?id=66462#c10 I am suggesting that there is a large known change in behaviour with recent Xservers which is very likely to impact upon you. I am sorry you find our requests for feedback frustrating, we too find it frustrating not to be in a position to test ideas and fixes ourselves, and very much rely on your good selves to both report issues and help us diagnose them. The frustration is not the comment itself, but the obstacle in needing to build a binary to be able to test the efficacy of the patch. Might having a Gentoo installation facilitate such tests by non-programmers like me who normally use a dpkg or rpm distro and don't how to use developer tools? -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] i810 only partially usable
On 2013-09-23 09:22 (GMT+0100) Chris Wilson composed:
On Sun, Sep 22, 2013 at 08:45:57PM -0400, Felix Miata wrote:
82810E DC-133 (GMCH)(rev 03)
...
*
Not good (openSUSE 12.2):
glamor-0.4.1-2.2.2
kernel-desktop-3.4.47-2.38
libdrm2-2.4.33-2.47.33-2.3.2
libdrm_intel1-2.4.33-2.47.33-2.3.2
(no Plymouth)
xf86-video-intel-2.20.3-1.8.1
xorg-x11-driver-video-intel-legacy-2.9.1-22.1.2
xorg-x11-server-7.6_1.12.3-1.9.1 (server 1.12.3)
highest (& initial) video mode available according to xrandr and
krandrtray: 1280x1024
PreferredMode is apparently ignored.
Broken by
commit 7bb653bedceb6180a0361ead1c612839e776ce98
Author: Olivier Fourdan
Date: Mon Oct 18 15:59:35 2010 -0400
modes: improve aspect ratio match for classic drivers
which filters the modes reported by the EDID to the largest builtin
mode.
diff --git a/hw/xfree86/common/xf86Mode.c b/hw/xfree86/common/xf86Mode.c
index 706ab64..2a11590 100644
--- a/hw/xfree86/common/xf86Mode.c
+++ b/hw/xfree86/common/xf86Mode.c
@@ -1869,10 +1869,10 @@ xf86ValidateModes(ScrnInfoPtr scrp, DisplayModePtr
availModes,
}
if (vx < virtX || vy < virtY) {
const int types[] = {
-M_T_BUILTIN | M_T_PREFERRED,
-M_T_BUILTIN,
M_T_DRIVER | M_T_PREFERRED,
M_T_DRIVER,
+M_T_BUILTIN | M_T_PREFERRED,
+M_T_BUILTIN,
0
};
const int ntypes = sizeof(types) / sizeof(int);
Should restore the intent back to
commit 81ef1b6d6063c20db4963abf7b7848e235aa4ebb
Author: Adam Jackson
Date: Thu Sep 14 19:18:58 2006 -0400
Mark EDID modes as driver modes. Infer virtual size from driver modes.
I don't know what to make of your response. I don't build packages. My i810
box is used only for seeking out and reporting regressions such as this. I'm
puzzled how I missed this for so long, although part of why is probably
attributable to loss of sysvinit causing me to have skipped over the openSUSE
12.3 development process with this machine. It's plenty slow, a 1GHz
Coppermine with PC100 RAM, so I don't boot it much.
Did Adam already fix this? Will you be including this among your next
submits? Do I need to file a bug first?
vttys are stable only as long as X never started, regardless whether
video= and/or vga= are present on cmdline. Only way I've found so
far to make them work reliably again once X is started is to reboot.
With various combinations of X running or not and video= and/or vga=
used, vttys get scrambled in various ways (font mismatched to row
and/or column counts of active mode).
While X is running but a vtty is active, X/KDE3 may abort spontaneously.
That sounds like the dangers inherent in UMS.
The whole paragraph? The last line only? Suggestions how to cope? I'm not
including nomodeset on any of my cmdlines. AFAIK, only my MGA systems are not
using KMS.
The biggest change here is the loss of XAA in Xorg.
This too says nothing I understand. Referring to XAA or EXA or the like has
no meaning to me. I'm not a programmer. I just test what others package, and
get frustrated by comments like this one:
https://bugs.freedesktop.org/show_bug.cgi?id=66462#c10
--
"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/
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] i810 only partially usable
82810E DC-133 (GMCH)(rev 03) Everything seems to be OK with these (openSUSE 12.1): glamor (no such package) kernel-desktop-3.1.10-1.29 libdrm-2.4.26-15.1.2 (no Plymouth) xorg-x11-driver-video-intel-legacy-2.9.1-13.1.2 xorg-x11-server-7.6_1.10.4-36.9.2 (server 1.9.3) 1600x1200 (which happens to be the EDID preferred mode) as specified via PreferredMode works. vga=8121 on cmdline works as expected on the vttys (no material BIOS VESA support available). http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log.gx110-os121-1600x1200x120OK * Not good (openSUSE 12.2): glamor-0.4.1-2.2.2 kernel-desktop-3.4.47-2.38 libdrm2-2.4.33-2.47.33-2.3.2 libdrm_intel1-2.4.33-2.47.33-2.3.2 (no Plymouth) xf86-video-intel-2.20.3-1.8.1 xorg-x11-driver-video-intel-legacy-2.9.1-22.1.2 xorg-x11-server-7.6_1.12.3-1.9.1 (server 1.12.3) highest (& initial) video mode available according to xrandr and krandrtray: 1280x1024 PreferredMode is apparently ignored. vga=8121 on cmdline works as expected on the vttys even after X is terminated. http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log.gx110-os122-bad1280x1024 * Awful (openSUSE 13.1 Beta 1): glamor-0.5.1-1.1 intel-gpu-tools-1.3-4.4 kernel-desktop-3.11.1-1 libdrm2-2.4.46-2.1 libdrm-intel1-2.4.46-2.1 (no Plymouth) xf86-video-intel-2.99.902-1.1 xorg-x11-server-7.6_1.14.3-1.1 (server 1.14.3) PreferredMode is apparently ignored. highest (& initial) video mode available according to xrandr and krandrtray: 1280x1024 vttys are stable only as long as X never started, regardless whether video= and/or vga= are present on cmdline. Only way I've found so far to make them work reliably again once X is started is to reboot. With various combinations of X running or not and video= and/or vga= used, vttys get scrambled in various ways (font mismatched to row and/or column counts of active mode). While X is running but a vtty is active, X/KDE3 may abort spontaneously. http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log.gx110-os131b1-0vga0video-1280x1024maxBAD http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log.gx110-os131b1-1vga1video-1280x1024maxBAD I was unable to find a bug matching this behavior on https://bugs.freedesktop.org/. Comments? -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Panning broken in i915?
On 2012/07/13 20:59 (GMT-0400) Felix Miata composed: I wouldn't ask here, except Bugzilla seems stuck on unreachable. Anyone know when it should be back online? Anyone know the status of panning? For me, mouse cannot move into the extended area, so only content can't go there, not my eyes. It's also broken on Nouveau. I finally got through to Bugzilla and found https://bugs.freedesktop.org/show_bug.cgi?id=39949 -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] Panning broken in i915?
I wouldn't ask here, except Bugzilla seems stuck on unreachable. Anyone know when it should be back online? Anyone know the status of panning? For me, mouse cannot move into the extended area, so only content can't go there, not my eyes. -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] i915 module does not find 82865G if configured as secondary
On 2011/10/08 17:25 (GMT+0200) Tempura San composed: The 82865G is onboard, but via BIOS the other (PCI) card is activated. In the end I would like to run Xorg on the 82865G card and keep the console output on the PCI card. Does your PC's BIOS setup not permit to assign priority to the onboard 865 chip? Is that ALG-2302 really a PCI card, or is it PCIe? -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] How can I set non-60Hz-Modes?
On 2011/08/11 10:10 (GMT-0400) Felix Miata composed: and if that didn't work, also adding Option"TargetRefreshRate" "60" That was supposed to be Option "TargetRefreshRate" "50". -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] How can I set non-60Hz-Modes?
On 2011/08/11 13:46 (GMT+0200) Dexter Filmore composed: On Thursday 11 August 2011 04:16:48 Felix Miata wrote: On 2011/08/11 03:45 (GMT+0200) Dexter Filmore composed: > Actually, right now about *all* these problems could be solved by moving > the machine to Win7. Are you sure? Is it possible only HDMI-1 works at 120, and the others at 60? Did you try plugging into any other HDMI ports? Is there a VGA port to try? There's pretty much one HDMI output on that board, one DVI, one VGA. Christopher James Halse Rogers replied to add 'Option "Monitor-HDMI2" "Monitor0"', making me think there actually was a #2 HDMI port. And why 120? Who would want 120? That was an error. I meant to type 100 as a consequence of your plasma's 50 doubling, not the 120 that many panel TVs offer. How exactly did you try to override VertRefresh? I would have tried something like VertRefresh 24-51 and if that didn't work, also adding Option "TargetRefreshRate" "60" and/or Option "DDC" "off" and/or Option "DefaultModes""on" and/or deleting your explicit modelines, allowing the built in modeline generator to do its job. -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] How can I set non-60Hz-Modes?
On 2011/08/11 03:45 (GMT+0200) Dexter Filmore composed: Actually, right now about *all* these problems could be solved by moving the machine to Win7. Are you sure? Is it possible only HDMI-1 works at 120, and the others at 60? Did you try plugging into any other HDMI ports? Is there a VGA port to try? -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] How can I set non-60Hz-Modes?
On 2011/08/10 19:58 (GMT+0200) Oliver Seitz composed: Felix Miata wrote: On 2011/08/10 14:15 (GMT+0200) Oliver Seitz composed: Configuration of software is not done through conf files anymore, it is done using hardware. If autodetection gives values you do not want, you have to alter the hardware. I can't imagine people trying to configure multihead without .conf files. How's that supposed to work? I've been exaggerating a bit, I must confess... But, to keep things straight, I really did multihead setup using xrandr in a startup script. You think mere mortals are going to find startup scripts, not to mention xrandr, easier to figure out than config files? Plus, in my experience, there are far too many different script file names and locations among various distros than X config files and locations. Not to say .config file setup is easy, because it's not, but to me they're the lesser evil. -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] How can I set non-60Hz-Modes?
On 2011/08/10 14:15 (GMT+0200) Oliver Seitz composed: Configuration of software is not done through conf files anymore, it is done using hardware. If autodetection gives values you do not want, you have to alter the hardware. I can't imagine people trying to configure multihead without .conf files. How's that supposed to work? -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] vsync on ttys with KMS
I run all my displays, LCD or not, at 60 vertical refresh. Flicker is a non-issue for these old eyes. Is there a way to force the kernel to use 60, or find out what is being used? On the p275 Trinitron I'm using right now, I doubt fc15's 2.6.38.2 is running 60, as the output is shifted so far left that at least 1/2" of output is hidden from view, and I don't want to be playing with the (hard to use) manual centering controls any more, risking running the display out of settings storage and FIFOing away previous settings I'll be using again. -- "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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] PCI configuration space of the VGA controller and laptop LCD picture quality.
On 2011/01/13 11:58 (GMT-0800) SD composed: I still can't figure out why Fedora (13,14,15) shows LCD picture much worse then opensuse 11.1. What does "worse" mean? Most people who see "worse" are actually complaining about fonts, and in most cases even then they don't define what is "worse" about the fonts. Can you upload screenshots of both so people can see what "worse" means? That said, Fedora sets some system wide variables that affect X quality/behavior in /etc/X11/Xresources: Xft.dpi Xft.hintstyle Xft.hinting openSUSE doesn't do that. If you comment those away in Fedora, or match the Xft.dpi number to your LCD's actual DPI, you may find the difference is reduced or disappears, particularly if actual DPI varies more than nominally from the Xft.dpi setting. OTOH, they may produce little or no improvement if you've set your DTE to force DPI or tweaked its font smoothing settings. If you need to comment further, also specify which DTE you use, as that can matter as well in future responses. As long as I still want to use Fedora on my laptop I would like to ask - can picture quality be spoiled by different PCI configuration? I highly doubt it, other than if it's wrong there's no picture to assess the quality of. -- "How much better to get wisdom than gold, to choose understanding rather than silver." Proverbs 16:16 NKJV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Problems configuring unique xorg.conf file
On 2010/09/26 20:09 (GMT) Nasa composed: > I should be a little more clear -- to create a modeline for a resolution > of 800x400 Are all your attempts so lax in typing accuracy? According to http://www.lilliput.cn/EBY701-NP.html you should be trying for 800x480. Typos compound your difficulty, especially if they go unnoticed. -- "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 Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Problems configuring unique xorg.conf file
On 2010/09/26 19:21 (GMT) Nasa composed: > I'm starting to look at the code and see if I can hardwire support > for vertical refresh rates greater than 60.0 (haven't figured that > out yet) It's rare for a flat panel display to either need refresh higher than "60", or product better performance using a supported refresh higher than "60". The reasons for using refresh higher than 60 on a CRT do not exist on flat panels. -- "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 Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Using quirks to fix incorrect Monitor physical size
On 2010/09/13 22:42 (GMT) Nasa composed: > Felix Miata wrote: >> Does Meego have /etc/sysconfig/videobios? I just discovered it on >> openSUSE >> that file does not exist. I've since discovered that was made obsolete nearly two years ago. > Checked the meego install and no that file doesn't exist -- good suggestion > though. > I also tried the VESA driver, which just ended up giving me a black screen. What about the fbdev driver? What about the intellegacy driver? I don't see intellegacy in the Meego repo, but openSUSE 11.3 has it, so maybe if Meego doesn't have it incorporated in some larger package you can boot some live CD or DVD that does have it to see if it can make your display work properly. Hmmm, IIRC a new quarterly Intel driver release is due RSN. Maybe that will be your answer. -- "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 Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Using quirks to fix incorrect Monitor physical size
Does Meego have /etc/sysconfig/videobios? I just discovered it on openSUSE 11.4. It contains: ## Path:System/Hardware/Graphicscard ## Description: Additional options for graphics cards ## Type:yesno ## Default: no # # Should the Intel(R) video BIOS be patched to let the X Server run with # resolutions unknown to the BIOS? Warning, this is potentially dangerous, # read the documentation in /usr/share/doc/packages/915resolution. # VIDEOBIOS_PATCH="no" ## Type:string ## Default: # # The options passed to 915resolution, usually 3 numbers: # the video mode to patch, X and Y resolution. # VIDEOBIOS_PARAMETERS="" Note /usr/share/doc/packages/915resolution on the i845G system where I found that file does not exist. -- "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 Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Using quirks to fix incorrect Monitor physical size
On 2010/09/13 11:42 (GMT) Nasa composed: > This isn't a laptop. It's a 7" monitor > (http://www.lilliput.cn/EBY701-NP.html), > that I am using in my carpc. I am presently try this with the IVI > version of meego (with it's own issues). Lilliput does provided drivers > for Windows, but nothing directly for Linux. I have also verified that the > monitor doesn't provide EDID data as the file size (I found were it's dump > to, > just can't recall right now) was 0. Talking to Lilliput themselves hasn't > been very helpful (I don't speak a 2nd language, and neither did the rep I > tried to talk too). Anything that is neither a standard format (4:3, 16:10 or 16:9) nor provides valid EDID is just plain broken. I'd return it. If it's too late for free return, maybe the vendor would allow exchange. If not, then try warranty repair. Maybe a Lilliput support manager can authorize an attempt to get it to output valid EDID either with a firmware update or otherwise. Again, what about VESA or FBDEV drivers? No help? -- "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 Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Using quirks to fix incorrect Monitor physical size
On 2010/09/13 10:10 (GMT) Nasa composed: >> Is there a way to tell the driver to use DisplaySize to pass the >> correct dimensions to >> the i915 driver? from my searches, I saw the following note: >> News: xf86-video-intel only supports KMS now >> 2010-02-11 - Jan de Groot >> With the move of xf86-video-intel 2.10.0 to extra, support for UMS has >> been removed from the intel driver. This means that KMS is a >> requirement now. >> Does this mean that there's no way to override incorrect (or in my >> case) missing EDID info? I am assuming so, >> which is why I am asking about quirks. Thanks in advance, > So... > Given the lack of a response, I am guessing this means the drivers don't > support this capability. Is there a reason for limiting user capabilities? > Removing users ability to work around hardware issues just seems like the > wrong way to go. At least in my humble opinion. I'm not implying what you're asking for is unreasonable or too much to ask, but have you tried Meego's vesa or fbdev drivers with KMS disabled? If those don't cut it for you, maybe you just need to wait a while longer for the Intel devs to replace more of what got discarded when UMS got dumped from its driver. Maybe you need to file an xorg bug to help that along. What was on the laptop when you bought it? You'd think the vendor would have shipped something works with its hardware. I can't tell from http://lists.freedesktop.org/archives/intel-gfx/2010-August/007907.html what it was you bought. -- "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 Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Intel 965 and Custom Resolutions
On 2010/08/31 18:32 (GMT-0400) Felix Miata composed: > On 2010/08/31 20:40 (GMT) Nasa composed: >> and the monitor.conf file: >> Section "Monitor" >>Identifier "VGA1" >>Option "useEDIDfreqs" "false" >>DisplaySize 152 91 >>VertRefresh 60 - 73 > Any improvement if you change 60-73 to 49-61 or add 'Option "NoDDC"'? >Option "PreferredMode" "800x600" Or set the preferred mode you actually want? -- "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 Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Intel 965 and Custom Resolutions
On 2010/08/31 20:40 (GMT) Nasa composed: > and the monitor.conf file: > Section "Monitor" >Identifier "VGA1" >Option "useEDIDfreqs" "false" >DisplaySize 152 91 >VertRefresh 60 - 73 Any improvement if you change 60-73 to 49-61 or add 'Option "NoDDC"'? -- "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 Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Problems configuring unique xorg.conf file
On 2010/08/26 21:56 (GMT-0400) Felix Miata composed: Future Intel/800x480 Googlers might welcome finding this thread extended, preferably to successful conclusion. -- "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 Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Intel 965 and Custom Resolutions
On 2010/08/31 10:03 (GMT) Nasa composed: > did I still miss something? Only the clairvoyant might know as long as you keep Xorg.?.logs and exact /etc/X11/xorg.conf.d/ content secret. -- "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 Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Intel 965 and Custom Resolutions
On 2010/08/30 16:44 (GMT) Nasa composed: > I tried to find out the same info -- with no success. The only possible > solution is to try and use xrandr to change the resolution after X is > started. Use a combination of CVT (to create modelines) and xrandr to > to change the resolutions. Did you miss http://lists.freedesktop.org/archives/intel-gfx/2010-August/007917.html or didn't it help any? -- "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 Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Problems configuring unique xorg.conf file
On 2010/08/26 23:14 (GMT) Nasa composed: > Given Meego's setup where is the appropriate place to put the xrandr > commands? I was confused on this point when I tried that before... I know nothing about Meego other than that you are using it. :-p > X seems to be started from 3 files in /etc/X11/xinitrc (xinitrc, > xinitrc-common, and Xclients) It worked for me in openSUSE 11.3 adding everything in xinitrc near the end, right before the actual window manager startup commands. An alternative that worked for me was using ~/.xinitrc and leaving /etc/X11/xinit/xinitrc untouched. > I opted to add the lines to xinitrc thus: ... > xrandr --newmode "840x480_60.00" 31.25 840 864 944 1048 480 483 493 500 > -hsync +vsync ... > Where I have it placed now doesn't work (after removing my edited xorg.conf, > I get > the original resolution back). So I must not understand where it should be > placed. > Could you enlighten me, *pretty please* :} I did more experimenting. It worked for me with no xorg.conf, modifying nothing in /etc/X11/xinit, and putting what used to work in the monitor section of xorg.conf into /etc/X11/xorg.conf.d/50-monitor.conf. http://fm.no-ip.com/Tmp/Linux/Xorg/50-monitor.conf.02-113-t2240-1600x1200x120-60_i845G worked for me to get 1600x1200 instead of the 1024x768 default, but you may need to add the above xrandr data as a Modeline in order to get your 800x480. -- "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 Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Problems configuring unique xorg.conf file
On 2010/08/26 10:47 (GMT) Nasa composed: > I am trying to configure a rather obscure resolution (800x480) which is the > native resolution for my monitor. The monitor doesn't provide EDID or DDC > information (it's connected over VGA). And the default settings by the > driver produces displays that don't fit the monitor properly. I would like > to construct a xorg.conf file with appropraite vertical refresh rates, > horizontal > syncs, and/or modelines to work correctly with the monitor. However, there > doesn't seem a way to turn off the driver defaults for those items. I tried > options > like NoDDC, UseEDID, etc with no luck. I also tried using xrandr to change > resolutions after X has started. The results end up being worse than the > intial problem I was trying to fix (ie: the screen is bigger than the area > available to display it). I expect my inability to find a suitable solution > is due to my lack of knowledge -- so I hope someone can fill me in to what > I am missing. Thanks in advance, > Chipset: 945GM >From openSUSE 11.3 on i845G http://fm.no-ip.com/Tmp/Linux/Xorg/xinitrc-113-t2240-1600x1200v1920 should serve as a template for you to construct an /etc/X11/xinit/xinitrc file with required xrandr commands included to be run _before_ $WINDOWMANAGER starts. Note that the reason for preferring high refresh rates on CRT displays does not exist on flat panel displays. I've yet to find any flat panel that doesn't work perfectly in close proximity to 60 if not exactly 60. So, K.I.S.S., and use CVT and/or GTF without bothering with refresh spec. 'gtf 800 480' will default to 60, which would invariably be just right. Supposedly xorg.conf can still be used with legacy Intel chips to do the same things as xinitrc/xrandr do, but I've yet to confirm it, succeeding only on MGA so far. -- "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 Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] 845 help
On 2010/08/01 20:49 (GMT+0200) Rüdiger Härtel composed: > I have a 845GL graphics chip and the driver reports nearly every time I use > my > copmuter that the GPU has hung up and acceleration is disabled. After this > happend a restart of X - which happens when I log off and on again - is not > possible anymore. > Is there any information I can provide to help finding the circumstances > that > lead to this behaviour? > My system: > http://www.smolts.org/show?uuid=pub_663f9f31-d4fc-4845-8d9b-04636d8df99d I have two 11.3 845G/GL rev01 systems, one from Dell/Foxconn, the other from Intel. On the latter, I just did startx/end (KDE4) session more than 20 times trying (with panning) to get vertical and horizontal DPI to match (instead of 121X120). /etc/X11/xinit/xinitrc: http://fm.no-ip.com/Tmp/Linux/Xorg/xinitrc-113-t2240-1600x1200v1920 /etc/X11/xorg.conf: http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.conf.0e-113-t2240-1600x1200v1920 ~/.xinitrc: http://fm.no-ip.com/Tmp/Linux/Xorg/dotxinitrc-113-t2240-845G-1600x1200v1920-120x120 On the other, repeated startx/killall startkde3 seems to be no problem either, with no ~/.xinitrc, stock /etc/X11/xinit/xinitrc and this xorg.conf: http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.conf.17-113-gx260-845G-1600x1200x120 -- "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 Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] need advices for chipset 82845G/GL
On 2010/07/22 23:49 (GMT+0200) david gastao composed: > I've got a Fujistu/Siemens Amilo L6820 with one of the Intel video chipset, > 82845G/GL. > I'm with the Linux distribution Ubuntu 10.04 and i've got video issues What make and model and size and type and resolution is your display? > (black screen time by time, How long is "by time "? > really bad video streaming). Streaming using which application? > Can you advice me which driver i should use to fix that pls? 10.04 automatically uses correct video driver for legacy Intel video. By default, it has no video configuration file as in past versions (/etc/X11/xorg.conf). If you need special settings you can make one with those settings in it. > It would be so helpfull. http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-t2240-i845G-buntu1004 is /var/log/Xorg.0.log from my computer with Intel motherboard and i845G video and Kubuntu 10.04. Maybe you can compare to yours for clues to problems. Mine seems OK. It uses a Sony/Dell Trinitron CRT. -- "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 Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [i845G] stuck in 1024x768
On 2010/06/13 23:10 (GMT+0100) Andy Lutomirski composed: > On Jun 13, 2010, at 9:49 PM, Felix Miata wrote: >> Using openSUSE 11.3M7 (1.8.0 server/2.11.0 AFAICT) I've been unable >> to figure >> out how to get the server to obey xorg.conf entries for NoDDC, >> NoRandr, >> PreferredMode or DisplaySize. Is it no longer possible to get my >> choice of >> resolution and DPI without reverting to one of the older X/driver >> versions >> that was perfectly happy to do 2048x1536 on whatever size display >> (IOW, >> whatever DPI I desire) I set it to use (and without _any_ modeline >> entries in >> xorg.conf)? >> Must I use /etc/X11/xorg.conf.d entries instead? If so, where are the HOWTO >> and valid entries catalog located? >> xorg.conf.new created by 'X -configure': >> http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.conf.new-t2240-os113-20100613a >> xorg.conf as last modified by me: >> http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.conf-t2240-s113-20100613a >> Xorg.0.log from last use of above xorg.conf: >> http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-t2240-s113-20100613a >> Note: My display produces neither valid EDID nor valid DDC. > Do xrandr --newmode and xrandr --addmode not work? Not so far. 'xrandr' & 'xrandr -q' can't open display. xrandr --help scrolls off the screen. 'xrandr --newmode `cvt 1600 1200`' produces syntax message. http://linux.die.net/man/1/xrandr shows only terse syntax with no examples. Google produced its usual zillion unhelpful hits, mostly about configuring multiple displays. This and more is why I inquired here. With xorg.conf as recently as last fall, no command line understanding was required, only following any of many widely available instruction examples, from which when correctly followed, X simply obeyed, _starting_up_ in the desired mode, doing automatically whatever it is that now requires output from gtf or cvt run separately beforehand. Just as importantly, I've not yet figured out why anyone should have to do manually (presuming they can even figure out how) what used to work automatically. For years, no modelines were in xorg.conf were required, and X just used the first usable entry on the applicable modes line in 'Section "Screen"'. Later someone decided a PreferredMode entry in 'Section "Monitor"' was required to perform the same function, but now it no longer works. Supposedly the overhaul of X begun two years ago was to make operation/startup/configuration (?more?) automatic, not less, but I, always using Trinitron CRTs, have only observed quite the contrary so far. X for me has regressed from the jet age back to piston engined biplanes without electric starters. -- "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 Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] [i845G] stuck in 1024x768
Using openSUSE 11.3M7 (1.8.0 server/2.11.0 AFAICT) I've been unable to figure out how to get the server to obey xorg.conf entries for NoDDC, NoRandr, PreferredMode or DisplaySize. Is it no longer possible to get my choice of resolution and DPI without reverting to one of the older X/driver versions that was perfectly happy to do 2048x1536 on whatever size display (IOW, whatever DPI I desire) I set it to use (and without _any_ modeline entries in xorg.conf)? Must I use /etc/X11/xorg.conf.d entries instead? If so, where are the HOWTO and valid entries catalog located? xorg.conf.new created by 'X -configure': http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.conf.new-t2240-os113-20100613a xorg.conf as last modified by me: http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.conf-t2240-s113-20100613a Xorg.0.log from last use of above xorg.conf: http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-t2240-s113-20100613a Note: My display produces neither valid EDID nor valid DDC. -- "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 Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] i915GM 2D+3D intel driver regression
On 2010/04/30 08:45 (GMT-0700) SD composed: > I have been using linux for 2 years already. And I use it on intel 915 GM > video card: > X uses 4% of CPU > SMplayer 10-12% of CPU. > GLXgear gives me: > 3216 frames in 5.0 seconds = 643.117 FPS > Now I tried Fedora13 (test) with intel driver: > And can you imagine GLXgear gives me: > 165 frames in 5.1 seconds = 32.612 FPS > Watching Xvid movie: > X uses ~40% of CPU > SMplayer ~10-20% of CPU. > So, for i915GM new driver is BIG BIG REGRESSION and big step backward. This regressive behavior is well known. F13 has not been released, so it's betaware. If you can't deal with bugs then don't replace what's working OK with development versions. Newer isn't always better. If it's working, don't try to "fix" it by "upgrading" to betaware. Meanwhile, someone must install the betaware to find the bugs. If you think your experience is unique, report in the appropriate manner. Did you look in bugs.freedesktop.org and/or bugzilla.redhat.com before installing F13 or comming here? Complaining here about a "big regression" is unlikely to be much help in getting it fixed. -- "Suppos [sic] a nation in some distant region, should take the Bible for their only law book, and every member should regulate his conduct by the precepts there exhibited. . . . What a Eutopa, What a paradise would this region be!"John Adams, 2nd US President Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
