LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 04-20-2008, 11:32 AM   #16
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,920

Rep: Reputation: Disabled

I think you should ask for support from your distribution.

If you're running the "stable" release of it, then there almost certainly aren't any new xorg packages to upgrade (meaning you screwed up).

If you're running the development version of it, then there are probably some important notes in the ChangeLog or elsewhere that you've neglected to read, and/or you didn't upgrade the other packages associated with it (IOW, you upgraded *only* xorg packages from the development version, leaving everything else with the packages from -stable). If that's the case, then yeah, it means you've screwed up.

Talk to arny.
 
Old 04-20-2008, 01:54 PM   #17
R03L
Member
 
Registered: Feb 2008
Distribution: mepis, ubuntu server ed. Debian. Redhat. Fedora, centos, LFS
Posts: 211

Original Poster
Rep: Reputation: 31
Quote:
Originally Posted by T3slider View Post
There are so many possibilities it's not funny. First of all, you need to learn to use links or lynx so you can post your xorg.conf (or, alternatively, learn some keyboard shortcuts so you can do it through X). It's incredibly difficult to "guess" the problem when it could be a really bad xorg.conf. Second, you built this Xorg yourself. Xorg is a huge set of programs, and it's entirely possible that you messed something up. Out of curiosity, WHY did you need to update Xorg so badly? If you really wanted a newer X than provided in 12.0, you could always try -current.

I realize my tone is not so nice, but after reading...

...I wonder if you truly want a working system.
i tried to update x.org server becouse i want to use
that aquarius plugin in compiz-fusion
and i get an error on compiz-fusion.
for transparant desktop u need to update x.org server
and for compiz-fusion to work on kde i solved this error message updating x.org server it's working i saw but now mouse is gone,,
 
Old 04-22-2008, 06:11 AM   #18
R03L
Member
 
Registered: Feb 2008
Distribution: mepis, ubuntu server ed. Debian. Redhat. Fedora, centos, LFS
Posts: 211

Original Poster
Rep: Reputation: 31
yes i did all the 180 packages.

http://www.linuxquestions.org/questions/slackware-14/compiz-core-fatal-no-composite-extension-636704/
this is why i updated my x.org
i i realy did lose that specific message.
 
Old 04-22-2008, 10:10 AM   #19
wes103
LQ Newbie
 
Registered: Sep 2004
Location: Eastern Pennsylvania, US
Distribution: Slackware
Posts: 21

Rep: Reputation: 15
Is there anything interesting in /var/log/Xorg.0.log ?
Search for both "mouse" and "Mouse".
 
Old 04-22-2008, 11:52 PM   #20
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,291

Rep: Reputation: 708Reputation: 708Reputation: 708Reputation: 708Reputation: 708Reputation: 708Reputation: 708
Quote:
Originally Posted by wes103
Search for both "mouse" and "Mouse".
Or use `grep -i mouse /var/log/Xorg.0.log` to cover all your bases.
 
Old 05-06-2008, 01:46 PM   #21
ryerke
Member
 
Registered: Dec 2006
Location: Fresno CA
Distribution: Slackware 13 Slackware 13.37 ARMEDSlack 13.37
Posts: 89

Rep: Reputation: 21
I'm also having the exact same issue. I went through the upgrade procedure that Pat outlines in CHANGES_AND_HINTS and UPGRADE.TXT from Slackware 12.0 to 12.1. Everything went smoothly with the exception of the loss of the mouse. I'm interested in the "/proc/dev/input/devices" resulting in Macintosh mouse button emulation. That seems to be the closest thing listed for a mouse. I also stopped getting the floating cursor on the console in user level 4. I don't know if that is a result of the upgrade, or if that could indicate that I have no mouse for xorg.conf to connect to.

I have to add that I use a Belkin KVM switch and I noticed that kvm's were mentioned in some of the comments as I looked for configuration options.

Everything in this post seems to be exactly the same as what I am experiencing.
 
Old 05-06-2008, 02:17 PM   #22
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,920

Rep: Reputation: Disabled
Quote:
Originally Posted by ryerke View Post
I'm also having the exact same issue. I went through the upgrade procedure that Pat outlines in CHANGES_AND_HINTS and UPGRADE.TXT from Slackware 12.0 to 12.1. Everything went smoothly with the exception of the loss of the mouse. I'm interested in the "/proc/dev/input/devices" resulting in Macintosh mouse button emulation. That seems to be the closest thing listed for a mouse. I also stopped getting the floating cursor on the console in user level 4. I don't know if that is a result of the upgrade, or if that could indicate that I have no mouse for xorg.conf to connect to.

I have to add that I use a Belkin KVM switch and I noticed that kvm's were mentioned in some of the comments as I looked for configuration options.

Everything in this post seems to be exactly the same as what I am experiencing.
What does "lsmod | grep psmouse" show?

-RW
 
Old 05-06-2008, 02:35 PM   #23
ryerke
Member
 
Registered: Dec 2006
Location: Fresno CA
Distribution: Slackware 13 Slackware 13.37 ARMEDSlack 13.37
Posts: 89

Rep: Reputation: 21
I don't get anything at all. After insmod .../psmouse.ko, everything started to work. I should have known that it would be that easy. What would be the convention to get that thing inserted at bootup?

Last edited by ryerke; 05-06-2008 at 02:43 PM.
 
Old 05-06-2008, 02:49 PM   #24
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,291

Rep: Reputation: 708Reputation: 708Reputation: 708Reputation: 708Reputation: 708Reputation: 708Reputation: 708
ryerke, what kernel are you using (vmlinuz-generic-smp-2.6.24.5-smp, vmlinuz-huge-smp-2.6.24.5-smp, vmlinuz-generic-2.6.24.5, vmlinuz-huge-2.6.24.5)? That's not the most relevant question since psmouse is built as a module in all kernels, but I just want to make sure you're using the right kernel. Have you tried `/sbin/modprobe psmouse proto=imps` as root? In /etc/modprobe.d/blacklist there's an explanation of psmouse stuff, and therefore the module is blacklisted and loaded manually by /etc/rc.d/rc.modules*, at least in Slackware 12.0 -- but this may have changed in 12.1. I think there's now a /etc/modprobe.d/psmouse file that dictates how the module gets loaded instead of blacklisting and manually loading in rc.modules*. The fact that it's still not loading properly may be because of an improper upgrade -- if it's still blacklisted in /etc/modprobe.d/blacklist (ie you didn't update that file [is there a .new file for that?]) and now is not getting loaded in /etc/rc.d/rc.modules*, it'll never get loaded. Try loading it manually (using the command above). If it works, try changing the blacklist file and making sure /etc/modprobe.d/psmouse exists and specifies the correct options -- or manually loading the module using /etc/rc.d/rc.modules*.
 
Old 05-06-2008, 02:55 PM   #25
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,291

Rep: Reputation: 708Reputation: 708Reputation: 708Reputation: 708Reputation: 708Reputation: 708Reputation: 708
Quote:
Originally Posted by CHANGES_AND_HINTS.TXT
The psmouse module is no longer blacklisted by default; instead, it is loaded
with the imps protocol per /etc/modprobe.d/psmouse -- if you need/want a
different protocol, edit that file. Note that options declarations have
no bearing on *if* a module is loaded - they only affect *how* it is loaded.
In other words, the module should now be loaded automatically (since it's no
longer blacklisted), and the options in /etc/modprobe.d/psmouse are the ones
applied when loading it.

The /etc/modprobe.d/blacklist file has been changed significantly; be sure to
move/merge the /etc/modprobe.d/blacklist.new file in its place. Also, you
must NOT leave a backup of the old blacklist file (such as blacklist.orig)
in /etc/modprobe.d/ -- ALL files in that directory are checked, so if a
module is blacklisted in *any* of them, it won't be loaded.
That's probably it there. Make sure you deleted the old blacklist file or it'll still get blacklisted.
 
Old 05-06-2008, 02:58 PM   #26
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,920

Rep: Reputation: Disabled
Quote:
Originally Posted by ryerke View Post
I don't get anything at all. After insmod .../psmouse.ko, everything started to work. I should have known that it would be that easy. What would be the convention to get that thing inserted at bootup?
First, ignore anyone who suggests editing rc.modules for now, as that's a last resort.

Second, look around in /etc/modprobe.d/ - what's happened is one of the following scenarios:
1. You still have both a 'blacklist' and a 'blacklist.new' file in there.
2. You have a 'blacklist' and a 'blacklist.orig' OR 'blacklist.bak'

If (1) is the case, then 'mv blacklist.new blacklist'
If (2) is the case, then 'rm blacklist.orig' or 'rm blacklist.bak'

If (1) is the case, then you need to search for more .new files in /etc (use 'find /etc -name "*.new"') to check and handle them accordingly.
If (2) is the case, then you probably used slackpkg to upgrade, and while that's fine, you need to be aware of this for future reference.

Either way, CHANGES_AND_HINTS.TXT documents this situation and what to do about it.

Last edited by rworkman; 05-06-2008 at 03:01 PM.
 
Old 05-06-2008, 03:14 PM   #27
ryerke
Member
 
Registered: Dec 2006
Location: Fresno CA
Distribution: Slackware 13 Slackware 13.37 ARMEDSlack 13.37
Posts: 89

Rep: Reputation: 21
Thank you so much. I moved all of the old info into the .new files and cp'd them to the original configs, and yet I forgot that blacklist will look for any file that says blacklist (.bak, .new, etc.) Anyway, I thought I would wait until I was graphical to do the cleanup. Just like me to put off the chores 'til later.

I don't have time to make sure this works, but I've got a good idea that you're right. Right now it's time for bed.

Thanks again,
Bert
 
Old 05-10-2008, 10:34 PM   #28
ryerke
Member
 
Registered: Dec 2006
Location: Fresno CA
Distribution: Slackware 13 Slackware 13.37 ARMEDSlack 13.37
Posts: 89

Rep: Reputation: 21
I removed the extra files in modprobe.d and that did the trick. I think I was looking for something more complicated and overlooked the obvious...especially when Pat V had included it in the CHANGES_AND_HINTS file. I still have some .new's to get rid of. I think there may be some from the 12.0 upgrade from 11.0. I was wondering if it will be necessary to merge the group, passwd, and shadow files as it seems the script for dealing with the .new's leaves them out. Is it safe to just delete the new ones that were installed?

Thanks again, and thanks, Robby, for all the work you do on the Slackware project.
Bert
 
Old 05-10-2008, 10:41 PM   #29
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,291

Rep: Reputation: 708Reputation: 708Reputation: 708Reputation: 708Reputation: 708Reputation: 708Reputation: 708
Don't overwrite the group, passwd and shadow files -- that'll destroy your user setup. You should be fine leaving them alone. If you did merge them you may have some difficulty logging in or your group assignments may change.
 
Old 05-11-2008, 04:46 AM   #30
ryerke
Member
 
Registered: Dec 2006
Location: Fresno CA
Distribution: Slackware 13 Slackware 13.37 ARMEDSlack 13.37
Posts: 89

Rep: Reputation: 21
Okay, I left them alone. Diff showed some changes but they seem inconsequential (an "x" in one of the fields) so I should be alright just to delete the .new files.

Much appreciated.
 
  


Reply

Tags
mouse, xconfig, xorg, xorgconf


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Updated X.org server loos usb mouse R03L Bluewhite64 2 04-18-2008 11:46 AM
hostname is not getting updated by dhcp server hv905c Linux - Server 2 11-14-2007 12:18 PM
Mouse Wheel in Xorg Sugarat Linux - General 8 09-03-2006 05:00 PM
recent dist-upgrade of xorg has killed my mouse (and thusly, xorg). Lokathor Debian 4 06-10-2006 05:52 AM
Updated system, now mouse wheel/buttons don't work dandrzejewski Fedora 1 03-06-2005 08:27 AM


All times are GMT -5. The time now is 12:59 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration