SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Thanks for the link. Before you replied I found the 1.2.2 package in the Slackware 13.1 source.
After a bit of futzing around I compiled that, and I'm happy to say it works (but only after I add a 50-synaptics.conf in /etc/X11/xorg.conf.d).
I don't know what you want to do with your 1.9.1 code base, but I can say that synaptics 1.3.0 does not work on a Fujitsu T900, and 1.2.2 does. (Slackware 64 13.1 (with Eric's compat32 stuff), I haven't tried a 32-bit version of S13.1.)
Cheers.
Last edited by zsd; 10-27-2010 at 06:41 AM.
Click here to see the post LQ members have rated as the most helpful post in this thread.
Thanks for the link. Before you replied I found the 1.2.2 package in the Slackware 13.1 source.
After a bit of futzing around I compiled that, and I'm happy to say it works (but only after I add a 50-synaptics.conf in /etc/X11/xorg.conf.d).
I don't know what you want to do with your 1.9.1 code base, but I can say that synaptics 1.3.0 does not work on a Fujitsu T900, and 1.2.2 does. (Slackware 64 13.1 (with Eric's compat32 stuff), I haven't tried a 32-bit version of S13.1.)
Having gotten the Synpatics touchpad working by reverting to synaptics driver 1.2.2, now I'd like to get the wacom capability of the screen on this Fujitsu T900 tablet PC.
The wacom stuff works under (*cough*)buntu 10.10.
There is no evidence of xorg trying to load the wacom driver.
Anyone here have a tablet PC who can comment on whether they are getting the wacom stuff to work?
On my 945GME (Acer eMachine), I cannot get OpenGL to work in KDE 4.5.1 with these testing packages, although all is OK on -current with KDE 4.5.1.
Just rebuilt the mesa-7.9 package adding the patch referenced here https://bugzilla.redhat.com/show_bug...iple&id=643399 and now I have OpenGL with the Desktop cube animation working.
This is the diff between the output from 'xdriinfo options i915' before and after.
Yeah, i requested that from rworkman a couple of days ago.
These xorg packages have been up for so long and gone through so many changes,
a log would make sense.
ChangeLog for the whiners ;-) * BUT READ EVERYTHING BELOW THE CHANGELOG *
20101028:
Lots of stuff prior to and on today, and I'm not even going to try
to remember all of it, but here are the high points:
talloc: Added (new package)
radeon-ucode: Added (new package)
20101029:
New mesa (4_rlw) with two more patches from git and a patch from
Kubuntu that should address some of the kde woes...
Updated pixman to 0.20.x series
I'm back after having "upgradepkg" Robby's X packages set.
Everything looks good but a few EEs in /var/log/Xorg.0.log:
[ 5631.602] (EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for device
[ 5631.610] (EE) PreInit returned NULL for "HP Laser Mobile Mouse"
This does not prevent X to start nor my mouse and keybord to work though.
I do not know what can cause this ; before installing all Robby's X packages I already used xf86-input-mouse-1.6.0, xf86-input-evdev-2.5.0 and xorg-server-1.9.1 and did not notice these errors.
I append full X log as well as custom /etc/X11/xorg.conf.d/50-mouse.conf. Could it be that I should have deleted the section with MatchIsPointer "on" in 10-evdev.conf?
Let me know if I should provide more information.
Oh and a little detail: If I am correct, in file /usr/share/X11/xorg.conf.d 'Option "XkbVariant" ""' causes a WW in the X log as the keyboard variant, if indicated, should be set to a valid (not null) string.
Other than that Nouveau is working fine here as you can see in X log.
Oh and I use a custom 2.6.36 kernel -- as 2.6.37-rc1 is not released yet
My .config is appended too.
Didier
[EDIT]I just noticed that I shoud have written "InputClass" instead of "InputDevice" in 50-mouse.conf. But after having edited this file and restarted X, mouse stayed in a small rectangle in the middle of the screen. So I deleted that file and the problem remains.[/EDIT]
Last edited by Didier Spaier; 08-15-2015 at 05:41 PM.
Didier, are you *sure* that your 50-mouse.conf stub is even required? If the scroll wheel is the only reason you have that, I would expect it to work correctly by default. However, maybe my expectations are bad
Anyway, what I *think* is happening is this: since you defined the device name and identifier, X is looking for them in early startup, but they don't yet exist at that point (hence the preinit NULL). Later on, they show up via the usual detection using udev properties, and all is fine (which is why everything works as expected).
I don't know about that inappropriate ioctl - that one's worth some googling or posting on the xorg mail list.
Didier, are you *sure* that your 50-mouse.conf stub is even required? If the scroll wheel is the only reason you have that, I would expect it to work correctly by default.
You are right, this stub is not required.and deleting it don't change anything. In fact I added it because I saw in googling sombebody suggesting to try to name the device in such a case.
Quote:
Anyway, what I *think* is happening is this: since you defined the device name and identifier, X is looking for them in early startup, but they don't yet exist at that point (hence the preinit NULL). Later on, they show up via the usual detection using udev properties, and all is fine (which is why everything works as expected).
Nope as deleting 50-mouse.conf don't change anything. And reverse (keeping 50.mouse.conf and 90-keyboard-layout.conf but deleting 10-evedev.conf) dind't change anything either: same errors in X log, still keyboard and mouse working properly.
Quote:
I don't know about that inappropriate ioctl - that one's worth some googling or posting on the xorg mail list.
OK Robby, I will further investigate both issues (not knowing if they are related to each other or not). Thanks for your time.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.