https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196678
--- Comment #175 from Chris Hutchinson <[email protected]> ---
(In reply to Niclas Zeising from comment #173)
Thank you for your reply, Niclas.
> As others have already told you, nVidia driver version
> 304 is not supported by xserver 1.20.
Yes. But there was evidence in comment #154 (a patch by Jan)
to Lena that work was being done.
> As for the other issues, I suggest that you try using
> xf86-input-libinput instead of xf86-input-evdev.
I installed xf86-input-libinput immediately after installing
xorg-server. As the pkg-message told me to do so. I also
added kern.evdev.rcpt_mask=6 to sysctl.conf(8). I also attempted
kern.evdev.rcpt_mask=12. Neither appearaed to have any effect.
> I also suggest that you try without any xorg configuration at all.
When I initiated the first test to see if it would work. There
was nothing in X11/xorg.conf.d/. I initiated Xorg -retro. I was
given a screen, and the mouse functioned. So I restarted X with
a DE designated in ~/.initrc. Where I found everything *almost*
worked. But the up arrow key didn't function. So no history recall
in my shell, and nearly impossible to edit files. It was then
that I began to experiment, in an effort to obtain a working
up arrow key, by adding/tweaking conf file(s). Borrowing from
examples in this thread. At this point, if starting moused, and
adding a simple mouse conf file, I have a mouse. This is
currently the only file I have in X11/xorg.conf.d/
setxkbmap -query:
rules: evev
model: pc105
layout: us
DETAILS:
FreeBSD 13.0-CURRENT r358902
ports are from HEAD at 2 days ago
NVIDIA GeForce 6150SE at 00@00:13:0
xf86-video-nv
mouse/keyboard are PS2
Thank you again, for taking the time to respond, Niclas.
--Chris
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-x11
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.