James Ausmus wrote: > > > On Fri, Jul 10, 2009 at 11:31 AM, Dale <[email protected] > <mailto:[email protected]>> wrote: > > James Ausmus wrote: > > > > > > > > > > Hi Dale - can you post your /var/log/Xorg.0.log and > /etc/X11/xorg.conf > > files? > > > > Thanks! > > > > -James > > Posted in another reply. Should be in the same thread. Sorry, I > should > have posted those before. > > > :) It's hard to remember all the details when your roof is on fire... > <grin> > > From that Xorg log, it does look like the NVidia binary driver is > being loaded/used - what indicators are you seeing that tell you that > the nv driver is being used? If it's just a missing NVidia splash > screen, maybe the updated NVidia driver has it off by default? > > For the mouse - things do look fairly normal from the log - however, > try the following (if you don't ahve the xinput command, it is > provided by x11-apps/xinput): > > xinput list > > This should show you a list of your X input devices - you should see > your mouse there. Mine reads: > > "Virtual core pointer" id=0 [XPointer] > Num_buttons is 32 > Num_axes is 2 > Mode is Relative > Motion_buffer is 256 > Axis 0 : > Min_value is -1 > Max_value is -1 > Resolution is 0 > Axis 1 : > Min_value is -1 > Max_value is -1 > Resolution is 0 > "Virtual core keyboard" id=1 [XKeyboard] > Num_keys is 248 > Min_keycode is 8 > Max_keycode is 255 > "No brand 4 Port KVMSwicther" id=2 [XExtensionKeyboard] > Type is KEYBOARD > Num_keys is 248 > Min_keycode is 8 > Max_keycode is 255 > "Logitech USB Optical Mouse" id=3 [XExtensionPointer] > Type is MOUSE > Num_buttons is 32 > Num_axes is 2 > Mode is Relative > Motion_buffer is 256 > Axis 0 : > Min_value is -1 > Max_value is -1 > Resolution is 1 > Axis 1 : > Min_value is -1 > Max_value is -1 > Resolution is 1 > "CHICONY HP Basic USB Keyboard" id=4 [XExtensionKeyboard] > Type is KEYBOARD > Num_keys is 248 > Min_keycode is 8 > Max_keycode is 255 > > > Then, take the name of the mouse from the list - in my case "Logitech > USB Optical Mouse", and run: > > xinput test <mouse-name> > > for myself it was xinput test "Logitech USB Optical Mouse" - with the > quotes. > > The move the mouse a little, and run the scroll wheel a little - you > should see something along the lines of: > > motion a[0]=2 > a[1]=-4 > > > motion a[0]=7 > a[1]=-5 > > > motion a[0]=2 > a[1]=-11 > > > motion a[0]=-4 > a[1]=-11 > > > motion a[0]=-9 > a[1]=-10 > > > motion a[0]=-7 > a[1]=-13 > > > motion a[0]=-6 > a[1]=-13 > > > motion a[0]=-6 > a[1]=-11 > > > motion a[0]=-5 > a[1]=-8 > > > motion a[0]=-4 > a[1]=-9 > > > motion > a[1]=-6 > > > > motion a[0]=-1 > a[1]=-2 > > > motion a[0]=-1 > a[1]=-1 > > > motion a[0]=-1 > a[1]=-1 > > > motion > a[0]=-1 > > > > motion a[0]=-2 > a[1]=-1 > > > motion > a[0]=-4 > > > > motion > a[0]=-5 > > > > motion a[0]=-7 > a[1]=-1 > > > motion > a[0]=-9 > > > > motion > a[0]=-9 > > > > motion > a[0]=-14 > > > > motion > a[0]=-14 > > > > motion > a[0]=-13 > > > > motion a[0]=-11 > a[1]=-2 > > > motion > a[0]=-11 > > > > motion > a[0]=-4 > > > > motion > a[0]=-2 > > > > motion > a[0]=-1 > > > > motion > a[0]=-1 > > > > motion > a[0]=-1 > > > > button press 5 > button release 5 > button press 4 > button release 4 > button press 5 > button release 5 > button press 5 > button release 5 > > > IMPORTANT: Make a note of which scroll direction you do first, then > second. In my case, I scrolled down first (button 5 press/release), > then up (button 4 press/release) - if you get different button numbers > for down/up scrolling, then we just need to adjust your ZAxisMapping > setting in xorg.conf appropriately - use whatever button number you > see when you scroll up as the first number in the setting, and then > the down scroll button number as the second number. > > If things are still not working, post the output of all the above > commands, and we'll take it from there. > > Hope that helps! > > -James > > > > Thanks. > > Dale > > :-) :-) > >
It does appear to be loading nvidia but I don't see the splash screen. I also notice that it takes longer to log out for some reason. It logs in like always, about 10 seconds or so, but when I log out, it takes 45 seconds or so. Maybe the splash screen is off by default. I dunno. I'm assuming you are using evdev and hal. I'm back to the old way. It's just easier for me to keep working, if I can get my wheel to work again. I have another install that I may play with some but it's not going to be on my main OS again. I'm waiting on something else. Someone mentioned devicekit is a 'up n comer'. Sounds good to me. Saves this for the other install. Dale :-) :-)
