Date: Wed, 04 Nov 2020 01:32:41 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 250826] x11/xorg incorrect autogenerated xorg.conf Message-ID: <bug-250826-7141-9GmU0jo55U@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-250826-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-250826-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250826 --- Comment #4 from Bill Blake <billblake2018@gmail.com> --- Loading i915kms into my kernel suffices to make X start and for X to get in= put from my keyboard. I can use either the one from GENERIC or the one compiled from ports. BUT. 1) This bug report is about the auto-generated xorg.conf. X should have detected the fact that I didn't have i915kms and not generated an xorg.conf that relied on it. I was able to tweak the auto-generated xorg.conf to mak= e it work without i915kms, so X should have been able to do the same. Alternate= ly, in 5.4.4 and 5.4.8 of the Handbook, where it says one should not create a config unless X autoconfig fails, it should suggest loading i915kms (or ano= ther driver) before creating a config. 2) Using i915kms merely creates new problems for me. First, a buglet: I happened to leave /etc/ttys as-is when I ran the GENERIC kernel and my normal /etc/ttys has a login on every tty that GENERIC allows, meaning that there were none for X. X should have complained and died.=20 Instead, it took ttyv0 for itself, leading to amusing behavior as it conten= ded with the shell for keyboard input. And an annoyance: I use ctwm as my window manager and I bound ALT + Page Do= wn and ALT + the arrow keys to various functions. While my other ALT bindings (using letters) work fine, those ALT bindings do not work at all. Presumab= ly, X is sending different keys to ctwm when I'm using i915kms than it does when I'm not. I'm not thrilled by the idea of trying to track down what it is actually getting.=20 And a deal-breaker: I am visually impaired and I have a nice big screen so = that I can see what I'm doing. At some point in the past, the vt driver decided= to make the screen 100x37 instead of 80x25. That was a pain, but I can still = read it. However, when I use i915kms, that 100x37 goes to 160x50 and I really c= an't read that without further damaging my back (because I have to lean way forw= ard to read the screen). There is no obvious way to change the screen size; vidcontrol doesn't seem to allow it. (vidcontrol -i mode shows no modes; trying to change the size gets "Inappropriate ioctl for device".) Since I = use the text screens extensively, this alone makes i915kms useless for me. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-250826-7141-9GmU0jo55U>