Sorry I don't understand that question.
There is no question. I'm merely suggesting some settings might have remained from your previous attempts at dealing with mouse issues.
Sorry I don't understand that question.
pkg info -a | grep input
:...
xf86-input-keyboard-1.9.0_4 X.Org keyboard input driver
xf86-input-mouse-1.9.3_3 X.Org mouse input driver
...
In addition to the drivers free-and-bsd mentioned, also check ifSo always double check the Xorg input drivers are installed
xf86-input-libinput
is installed.LoadModule: "radeon"
No drivers available.
kld_list="/boot/modules/radeonkms.ko"
no screens found (EE)
List of video drivers:
scfb
modesetting
vesa
Built from ports but don't remember ever fiddling with those options. Maybe you're right here and I did something. Which may also be the case with the OP.Those drivers (x11-drivers/xf86-input-keyboard, x11-drivers/xf86-input-mouse and x11-drivers/xf86-input-libinput) are installed as a dependency of x11-drivers/xorg-drivers which in turn is a dependency of x11/xorg. So unless you are building from ports and changed the build options of x11-drivers/xorg-drivers those should be installed.
LoadModule: "radeon"
Failed to load module "radeon" (module does not exist, 0)
modesetting: Driver for Modesetting Kernel Drivers: kms
modeset(0): claimed PCI slot 1@0:5:0
...
glamor0: Failed to initialize glamor at ScreenInit() time.
AddScreen/ScreenInit failed for driver 0
I am fairly certain you don't. If the drm-kmod is loaded you use the modesetting driver with it. But what do I know, I am a long-term nvidia userNot sure how that helps, but good to know. My /var/log/Xorg.0.log says:
I guess the question is how do I load the radeon driver into Xorg then?Code:List of video drivers: scfb modesetting vesa
Mesa 18.3.2 implementation error: Invalid GLSL version in shading _language_version()
AddScreen/ScreenInit failed for driver 0
UnloadModule: "radeon"
Unloading radeon
glamor0: Failed to get GLSL version
modeset(0): Failed to initialize glamor at ScreenInit() time.
Fatal Server error:
AddScreen/ScreenInit failed for driver 0.
There are reports that users on i386 hardware have problems using the drm-kmod package. A workaround for this is to disable PAE via /boot/loader.conf: hw.above4g_allow=0
xauth .serverauth
pw groupmod video -m slurms || pw groupmod wheel -m slurms.
I added this. Nothing really has changed. It was a good suggestion though. Openbox is actually working fine now once again. It is Gnome desktop that is freaking out on me for some reason. A task for tomorrow. Thanks for the help as always!OK, here is another one Is your very old notebook actually x86 or x86_64 architecture? Here is why it seems to matter:
I wouldn't recommend GNOME for a very old laptop.I only installed the drm-kmod drivers last time. I wonder if the extra drivers are working against me this time?
...
It is Gnome desktop that is freaking out on me for some reason.
Thanks, I will give it a try. I kind of enjoy trying to configure Openbox right now. It is nice for a low resource computer. Do you know any guides for tint2, wbar, and openbox? Also, is there a way to have the FreeBSD handbook as an offline resource in the event I make another mistake (not that something like that would ever happen to me, but hypothetically! )? Also, feh is not loading my wallpaper when I start openbox. My autostart.sh looks like this now:You know, right now I, personally, am quite satisfied with FVWM2 and the apps I know I need. This one will run well even on a very old laptop . I'm tired of GNOME as it adds absolutely NOTHING to my configuration. Unless it be a bunch of services & apps I never use.
#!/bin/sh
(sleep 2 && tint2)
(sleep 2 && wbar)
(sleep 2 && feh --bg-scale '/home/user/wallpapers/WinterPath.jpg' &)
Download links for the FreeBSD handbook can be found in the Abstract section of the handbook on page 1.Also, is there a way to have the FreeBSD handbook as an offline resource in the event I make another mistake (not that something like that would ever happen to me, but hypothetically! )?