Date: Fri, 27 Sep 2019 18:39:10 +0300 From: "Jukka A. Ukkonen" <jau789@gmail.com> To: freebsd-amd64@freebsd.org Subject: i915kms question Message-ID: <f1bd5a0b-80c6-b9bc-4538-b73badae0a21@gmail.com>
next in thread | raw e-mail | index | archive | help
Hello all,
I recently bought a 7" TFT the dimensions of which are natively
1024x600 pixels and in text mode 128x36 assuming the 8x16 font
is used. It seems that whatever I do the kernel stubbornly ends
up assuming 160x64 dimensions in text mode which using the 8x16
console font is the same as 1280x1024. Obviously some text tends
to disappear beyond the right edge of the screen. Similarly 28
lines of text roll over the lower edge of the screen.
The graphics device to which the display device is connected
(via HDMI) is ...
# pciconf -lv vgapci0
vgapci0@pci0:0:2:0: class=0x030000 card=0x0f318086 chip=0x0f318086
rev=0x11 hdr=0x00
vendor = 'Intel Corporation'
device = 'Atom Processor Z36xxx/Z37xxx Series Graphics & Display'
class = display
subclass = VGA
I have set the following in /boot/loader.conf ...
kern.vt.fb.default_mode="1024x600"
kern.vt.fb.modes.HDMI-A-1="1024x600"
i915kms_load="YES"
Is that an indication that the i915kms module does not support
this particular graphics hardware model?
I also tried starting X11 on the system just to get a bit more
info about what is going on. That did not work out either.
I got the following error messages ...
X.Org X Server 1.18.4
Release Date: 2016-07-19
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD 11.2-RELEASE-p14 amd64
Current Operating System: FreeBSD xyzzy 11.3-STABLE FreeBSD 11.3-STABLE
#0 r351588: Thu Aug 29 02:09:40 UTC 2019
root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
Build Date: 21 September 2019 01:41:58AM
Current version of pixman: 0.38.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Sep 27 17:46:58 2019
List of video drivers:
modesetting
(++) Using config file: "/root/xorg.conf.new"
(==) Using system config directory "/usr/local/share/X11/xorg.conf.d"
(EE)
(EE) Backtrace:
(EE) 0: /usr/local/bin/X (OsInit+0x37a) [0x5baf8a]
(EE) 1: /lib/libthr.so.3 (_pthread_sigmask+0x53e) [0x80260a17e]
(EE) 2: /lib/libthr.so.3 (_pthread_getspecific+0xdef) [0x802609f8f]
(EE) 3: ? (?+0xdef) [0x7ffffffffdf2]
(EE) 4: ? (?+0xdef) [0xdef]
(EE) 5: /usr/local/bin/X (InitOutput+0x128c) [0x482e5c]
(EE) 6: /usr/local/bin/X (remove_fs_handlers+0x3bb) [0x43c7cb]
(EE) 7: /usr/local/bin/X (_start+0x95) [0x425145]
(EE) 8: ? (?+0x95) [0x800845095]
(EE)
(EE) Segmentation fault at address 0x0
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for
additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
For my eyes that is uninformative. Instead of complaining about
what it cannot do X falls on its face.
What might be the problem(s)?
Is there anything else meaningful I could test to collect more
info?
--jau
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f1bd5a0b-80c6-b9bc-4538-b73badae0a21>