Bug 210742 - intel Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller and 3440x1440 resolution
Summary: intel Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller and 3440x144...
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 10.3-RELEASE
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-01 12:33 UTC by delleceste
Modified: 2020-09-30 17:04 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description delleceste 2016-07-01 12:33:20 UTC
Hello.
I've just received a new 34" Dell monitor, but I am unable to start X on freebsd.
When I bring resolution above 2560x1080, for example 2560x1440 or 3440x1440 (which is the resolution I use in Linux), the screen goes off and the only thing I can do is restart the computer with Ctrl Alt Canc. I can't switch back to text console.

Is this resolution too high for the current i915kms driver?
Is something I can do?

dmesg says:

iic6: <I2C generic I/O> on iicbus6
iic7: <I2C generic I/O> on iicbus7
iicbus8: <Philips I2C bus> on iicbb4 addr 0x0
iic8: <I2C generic I/O> on iicbus8
iic9: <I2C generic I/O> on iicbus9
iicbus10: <Philips I2C bus> on iicbb5 addr 0x0
iic10: <I2C generic I/O> on iicbus10
iic11: <I2C generic I/O> on iicbus11
iicbus12: <Philips I2C bus> on iicbb6 addr 0x0
iic12: <I2C generic I/O> on iicbus12
iic13: <I2C generic I/O> on iicbus13
info: [drm] MSI enabled 1 message(s)
info: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
info: [drm] Driver supports precise vblank timestamp query.
drmn0: taking over the fictitious range 0xe0000000-0xf0000000
info: [drm] Enabling RC6 states: RC6 off, RC6p off, RC6pp off
info: [drm] Connector VGA-1: get mode from tunables:
info: [drm]   - kern.vt.fb.modes.VGA-1
info: [drm]   - kern.vt.fb.default_mode
info: [drm] Connector HDMI-A-1: get mode from tunables:
info: [drm]   - kern.vt.fb.modes.HDMI-A-1
info: [drm]   - kern.vt.fb.default_mode
info: [drm] Connector DP-1: get mode from tunables:
info: [drm]   - kern.vt.fb.modes.DP-1
info: [drm]   - kern.vt.fb.default_mode
info: [drm] Connector HDMI-A-2: get mode from tunables:
info: [drm]   - kern.vt.fb.modes.HDMI-A-2
info: [drm]   - kern.vt.fb.default_mode
info: [drm] Connector HDMI-A-3: get mode from tunables:
info: [drm]   - kern.vt.fb.modes.HDMI-A-3
info: [drm]   - kern.vt.fb.default_mode
info: [drm] Connector DP-2: get mode from tunables:
info: [drm]   - kern.vt.fb.modes.DP-2
info: [drm]   - kern.vt.fb.default_mode
info: [drm] Connector DP-3: get mode from tunables:
info: [drm]   - kern.vt.fb.modes.DP-3
info: [drm]   - kern.vt.fb.default_mode
fbd0 on drmn0
VT: Replacing driver "vga" with new "fb".
info: [drm] Initialized i915 1.6.0 20080730 for drmn0 on minor 0
error: [drm:pid871:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 17000000, was 12000000
pid 931 (zeitgeist-datahub), uid 1001: exited on signal 6 (core dumped)

Xorg.0.log does not report any (EE) error message, apart from fbdev module not found.

Ok with resolutions < 2560x1440.

I'm setting
                                                     
device         vt 

and

kldload i915kms

Thanks for any help.

Giacomo, Italy.
Comment 1 Alexey Dokuchaev freebsd_committer 2020-09-28 18:28:41 UTC
Do you still experience these problems with recent versions of FreeBSD and graphics stack + video drivers?  Note that DRM support had moved out of the base system/kernel to the `graphics/drm-*-kmod' and `graphics/gpu-firmware-kmod' ports.

Your report was against 10.3-RELEASE which went out of support long time ago.  Please update to contemporary, supported FreeBSD version and reconduct your tests.

Adding x11@ to CC list so it can be tracked while originally filed under base system/kern.
Comment 2 delleceste 2020-09-30 11:44:57 UTC
Hello Dear Alexey. I have no installation at the moment to provide a reply. Yes it is an old issue, I suggest closing it as I think it will have been solved in the meantime.
Regards