Unable to configure wireless mouse

Hello Archers,
An ubuntu convert myself is in need of some help configuring my Logitech Wireless Mouse. I'm posting relevant device information and sections from my xorg.conf. Any help is much appreciated.
PS: The mouse worked fine in Ubuntu and is also working fine with Vista.
keerthi ~ $ lsmod | grep evdev
evdev 8192 10
keerthi ~ $ cat /proc/bus/input/devices
I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/devices/virtual/input/input0
U: Uniq=
H: Handlers=mouse0 event0 ts0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3
I: Bus=0011 Vendor=0002 Product=0008 Version=0000
N: Name="PS/2 Mouse"
P: Phys=isa0060/serio1/input1
S: Sysfs=/devices/virtual/input/input5
U: Uniq=
H: Handlers=mouse1 event5 ts1
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3
I: Bus=0003 Vendor=046d Product=c51a Version=0111
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:1d.3-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.3/usb4/4-2/4-2:1.0/input/input9
U: Uniq=
H: Handlers=mouse3 event9 ts3
B: EV=7
B: KEY=ffff0000 0 0 0 0 0 0 0 0
B: REL=143
I: Bus=0003 Vendor=046d Product=c51a Version=0111
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:1d.3-2/input1
S: Sysfs=/devices/pci0000:00/0000:00:1d.3/usb4/4-2/4-2:1.1/input/input10
U: Uniq=
H: Handlers=kbd event10
B: EV=f
B: KEY=7fff ac3027 bf004444 0 0 1 f80 8a37c000 667bfa d9415fed 8e0000 0 0 0
B: REL=40
B: ABS=1 0
xorg.conf
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse1" "SendCoreEvents"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "synaptics"
Option "SendCoreEvents"
Option "Protocol" "auto-dev"
Option "SHMConfig" "on"
Option "LeftEdge" "1700"
Option "RightEdge" "5300"
Option "TopEdge" "1700"
Option "BottomEdge" "4200"
Option "FingerLow" "25"
Option "FingerHigh" "30"
Option "MaxTapTime" "180"
Option "MaxTapMove" "220"
Option "VertScrollDelta" "100"
Option "MinSpeed" "0.18"
Option "MaxSpeed" "0.25"
Option "AccelFactor" "0.0010"
EndSection
Section "InputDevice"
Identifier "Mouse1"
Driver "evdev"
Option "Name" "Logitech USB Receiver"
EndSection
Thanks.

Never mind. Figured out myself. Just changed "ServerLayout" section as below and that fixed the issue. I'm now able to use touchpad and wireless mouse as well.
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "SendCoreEvents"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Similar Messages

Hp touchpad unable to configure wireless print were do i find IP for printer

I have a secure system . Touchpad lets me do anything but print. when I try to set up it can not find my printer. It asks for the IP address for the printer. I was able to print until i set up a secure site.
I also have a laptop that is doing the same thing my printer is an officejet j6450 wireless my op sys is win 7 I have downloaded all patches and software for win7. unable too print.

Yes, your Norton could be in the way. Have you added Norton since you installed your printer or was it there before?
Go to Control Panel > Printers and delete the printer, then re-add it:
1. Make sure the printer is turned on and connected to your network. Verify that you can access the printer's internal web page by browsing to its IP address before continuing. Print a Wireless Network Test to get the IP address.
2. Click >> Start >> Control panel >> Printers.
3. Click the Add a printer
4. Select Local printer
5. Select Create a new port and select Standard TCP/IP Port and click Next button.
6. Under Device type, select TCP/IP Device. Under Hostname or IP address, enter the printer's IP address. Click Next.
7. Select Hewlett-Packard from the list of manufacturers and select and select your printer model. Click Next.
If your printer model was not listed, then select Have Disk, browse the HP CD that came with your printer and select the first file that starts with hp and ends with inf. Click Open then OK. Select your printer model. Click Next.
8. If you are asked, use the currently installed driver.
9. It will ask for the Printer name -- enter a new name or use the existing one. This will be the name of the printer that you select from other applications.
10. You may be asked to share the printer. Choose NO.
11. The Print Test Page box appears. Go ahead and print it.
12. Click Finish.
Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
I am employed by HP

All in one printer j6480 unable to configure wirelessly

i had the wireless feture installed but now it doesn't work tried to reconfigure but no resolution. I downloaded the drivers from hp but when it opens the graphics are there but no text. really frustrated. been going around in circles.

OK, disconnect the USB cable and Reset the Printer back to Factory Defaults.
Now download and install the full featured software here.
http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?cc=us&dlc=en&lc=en&product=3635378
Follow the instructions perfectly. If it told to plug in the USB cable do so only when asked.
Say thanks by clicking the Kudos Thumbs Up to the right in the post.
If my post resolved your problem, please mark it as an Accepted Solution ...
I worked for HP but now I'm retired!

Unable to configure magic mouse

This has been a problem since I got the magic mouse. When I attempt to set it up in preferences it says "no mouse found". However, I am able to pair it and use it as a normal mouse.
I applied the software update that was recommended but now that I read the instructions carefully I see that it says to pair with the mouse BEFORE installing the update and I'm not sure what order I did it in. Does it matter?
Until now I was using a beta version of a 3rd party program but the developer has stopped work on it (it worked perfectly for me without messing around with software updates.)
Has anyone figured out a workable solution?

Patricia,
In system Preferences > mouse. Compare the screen to the one at the bottom of this page:
http://www.apple.com/magicmouse/
If you see the demonstration video screen of the gestures than you have the proper software and setup.
If not than try pairing the mouse in System Preferences > Bluetooth > "+" icon below the list.
Regards,
Captfred

My wired Apple Magic Mouse is frozen and I am unable to move around on my Mini Mac. I receive a window saying the computer cannot locate a wireless mouse. How do I get my mouse to work again.

My Magic Mouse is frozen. How do I get it to work again? Also I keep getting a window that says it cannot locate my wireless mouse. I do not have a wireless mouse.

Got confused between your header question about a wired mouse and the main question about a wireless mouse. You said your magic mouse was frozen and added you do not have a wireless mouse. Problem is ... the magic mouse is wireless. The original mighty mouse was the corded version.
The wired mouse is a regular problem. After two to three years it tends to clog up. You can clean it (to a degree) as follows.
Using an alcohol moistened, not wet, cotton bud, scratch at the mouse ball for a minute or so. Then turn it upside down and on a clean piece of thick white paper or card on a firm surface, vigorously rub the mouse ball on the paper in a regular figure of eight. Do this for a minute or so and occasionally tap the mouse on the paper. This will help dislodge bits of fluff etc. Then try again

How to Configure Mighty Mouse in Windows 7?

How to Configure Mighty Mouse in Windows 7?
For example the 3rd and 4th Buttons on the Mighty Mouse.
How to configure those actions in Windows 7?

There is no need for additional drivers.
Why?
If you have a Wireless Mighty Mouse you have to turn your computer visible for other devices in the Bluetooth preferences - then simply search for Bluetooth devices, connect - done!
To configure the Mighty Mouse's buttons, you might want to have a look at a tool called X-Mouse Button Control (http://www.highrez.co.uk/downloads/XMouseButtonControl.htm).

Wireless mouse and Keyboard Issue after closing the lid - external display

Can anyone give any insight. Recent purchase of a new Late 2008 15" MBP. I have connected it to an external 24" Apple monitor on my desk and use a wireless mouse and wireless keyboard on my desk top. I have configured the laptop to wake on bluetooth devices. So here is the problem: The laptop when the lid is up recognizes the bluetooth keyboard and mouse. I close the lid/screen. Laptop powers down... the after several seconds I move the mouse and the laptop comes alive... But after that there are no bluetooth devices attached. When I use the mouse, I get "connection lost" with a white figure of the mighty mouse on the screen. The wireless keyboard is not there and I have to open the lid and manually find the mouse and reconnect. The keyboard seems to work however....
Apple..... any thoughts..... anyone?????

Hi Stentdoc; I'm thinking, 'connection lost ~= sorta low AA batteries in the Mighty Mouse? (I would put in fresh AA batteries in the mouse and keyboard, to eliminate as an issue that the 'connection lost' is due to low batt voltage; that this is causing the failure to wake.) ... then, in System Preferences > Hardware > Energy Saver, settings for Power Adapter > Sleep, set to "never" for "Put the computer to sleep when it is inactive for ..." to eliminate that as a conflict when trying to wake with bluetooth from sleep induced by closing the lid ...
Check your current "Sleep" setup (I left my MBP as "3")
go to Utilities > Terminal
After you launch Terminal, the first step is to determine which sleep mode your Mac is currently using. You can both view and change the sleep mode using the Unix program pmset. To see your current settings, type (or, copy and paste)
pmset -g | grep hibernatemode
press 'enter'
You should see something like this:
$ pmset -g | grep hibernatemode
hibernatemode 3
So your machine is using mode 3 ... thanks to the documentation for the handy Deep Sleep Dashboard widget, which puts your machine immediately into hibernation mode (so you don’t have to yank all the power sources to invoke it):
* 0 - Old style sleep mode, with RAM powered on while sleeping, safe sleep disabled, and super-fast wake.
* 1 - Hibernation mode, with RAM contents written to disk, system totally shut down while “sleeping,” and slower wake up, due to reading the contents of RAM off the hard drive.
* 3 - The default mode on machines introduced since about fall 2005. RAM is powered on while sleeping, but RAM contents are also written to disk before sleeping. In the event of total power loss, the system enters hibernation mode automatically.
also, I enabled this (to change back, input "lidwake 1":
go to Utilities > Terminal
type in sudo pmset lidwake 0 then "enter"
it will ask for your password. type it in, that's it!
Now, when your computer is sleeping with the lid closed, when you open the lid nothing happens until you press any key ... nice: keeps it off when accidentally opened, like in a backpack?
WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.
To proceed, enter your password, or type Ctrl-C to abort.

New Intel Mac Mini - wireless mouse v slow

Hi all
I've just bought my first MAC, a nice core duo intel mini. Having used PCs for years it came as a nice suprise to boot up and configure everything in next to no time.
However.....
I'm using a apple wireless keyboard and mouse. The keyboard seems to be fine, but the mouse is very very slow and jerks around a lot. If I switch to a (dare I say it) Microsoft wireless USB mouse, it works fine, no speed loss at all.
I guess it's something to do with the bluetooth and airport clashing? Or maybe I just have a duff wireless mouse?
Any mac gurus who can help me out?
TIA
Tim

I'm using this in my living room, and when I'm on the couch about 10 feet away it's a lot like having an extremely dirty non-optical mouse in that, as you move the cursor, it's constantly getting "stuck" and doesn't move as far as you expect, in a random sort of way. In addition, the cursor's movement is a little behind the mouse's movement.
If I put the mouse next to the computer, the problem goes away.
This in addition to the Airport signal problems indicates that it's an RF problem - poor antenna, shielding due to the enclosure, interference due to the new circuitry - something like that. I'm using the new mini in the same location as the old one, and I'm using the mouse in the same location. The new one has problems and the old one doesn't.

Need help identifying Apple Wireless Mouse

I was given a PowerBook G4 laptop at a recent Mac user group meeting. My plan for the computer is to donate the laptop and the parts and pieces given to me to a local agency. The agency will then give it so some family that needs but can't afford a computer.
The computer came with Tiger, and I have the disks. But the (presumed) original owner has installed 10.5 Leopard and I have the disk for that.
In looking around Apple, I think this is a bluetooth version of the Mighty Mouse. But I've been unable to locate a photo that matches this mouse.
It looks like a Mighty Mouse on the outside, but remove the battery cover and it doesn't match any photo and/or manual I've found.
At the end of the mouse where the sliding switch/LED cover is located, and under the cover, there is a sliding switch marked + and -. On the batt cover, the Model is A1015 but a search has returned 0 results.
I assume that to turn the mouse on, you slide the cover to expose the LED light. And, the light should turn on. But, it doesn't. The batteries are good.
In looking at the mouse, I think the sliding cover should depress what I'll call a switch, ahen when I manually depress the switch, the LED turns on, and is discovered. Without the light on, the computer will not discover the mouse. After discovery, and continuing to hold the switch down to keep the LED on, the mouse will not pair up to the computer. Just for FYI, I get the same results trying to pair to my iMac with Snow Leopard 10.6.8.
Which leaves me with the following questions:
Is this a Mighty Mouse?
Is there a manual and/or photo of this mouse somewhere?
Should the red LED turn on when the sliding cover exposes the LED?
Will it only work with Tiger?
Is there something small that is missing from the battery cover that would depress the switch properly?
Does it only work with Tiger?
What does the switch with the + and - do?
Ken

Hi, twtwtw,
well, without having it in hand I can't really see how it's supposed to attach or what exactly it does.
Photos of the battery cover and spring disasembled and assembled.
https://www.dropbox.com/s/lpw15yseg0a5w2m/Battery%20cover%20unassembled.jpg
https://www.dropbox.com/s/56sbnv31usewthr/Battery%20cover%20assembled.jpg
I just have the pieces laying in the correct position, no permanent repair. Would have simply thrown them on the scanner, but the all-in-one unit with scanner that was installed was removed yesterday to be donated with the laptop mentioned in my original post.
The round end of the spring pops the battery cover off when the latch is released. The other end depresses the switch in the mouse when the slide in the battery cover is moved.
it looks like they can be taken apart - there's a teardown of a different model at ifixit.com, which you might be able to adapt.
The wired version of a mouse similar in construction to that unit came with my iMac. When the trackball stopped scrolling, I found out you had to end up using Super Glue to reassemble, and that's no way to design a product, IMO. But, I always hated that mouse, it didn't fit my hand, and typing on the keyboard reminds me of the horrible "chiclet" keypads of yesteryear, and I replaced both with an old Apple Pro keyboard and a Microsoft USB wireless mouse that actually fit my hand!!! What a concept!
The thing at the top (between the +/-) looks more like a latch than a switch to me. is it holding the bottom plate in place?
There is the proverbial Tab A on the cover that fits into Slot B on the mouse, but the the sliding thing does nothing to affect the tab/slot that I can determine. Possibly, it may control the amount of movement vertically you apply to get a "mouse press", but at the moment I've not tested that theory.
I think the +/- bit really is just a guide for battery installation.
"Illogical", as Mr. Spock would say. The orientation of the +/- is 90º to the battery installation. And both batteries are installed with the + end towards this end of the mouse.
if attaching the the piece of metal is just a matter of broken pins, though, you could try super-gluing it in place.
Super glue was my first thought, but spring steel is hard to get liquid type adhesives to adhere to. I also thought of using Gorilla Glue, if you're familiar with it. It's hard to find stuff that Gorilla Glue won't bond to with some degree of success.
I dug out my freestanding magnifier, and it almost looks like the "pins" probably had an upper, smaller in dia. part, that may have been melted over the spring to hold the spring in place.
and no matter what you say, tape is always an option.
LOL! Hope that was a joke for real, as that never an option for my repairs. If done, it's cheap and cheezy, as if you don't care what kind of workmanship you have.
With respect to the link... did you seriously keep hitting that link and sitting through the sarcasimation, rather than typing the words into a new google window yourself? Heck, you could have copy/pasted the text instead of typing it, or bookmarked the resulting google page for future reference, or..., or...
To start with, Google is almost never my search engine of first choice. Why? I've not trusted them with anything since they were caught violating privacy issues, more than once. My first choices are DuckDuckGo, Startpage, and IxQuick, because those search engines do not track your searches and surfing habits. Where I go and what I do is no one's business. I don't want that info given/sold/stolen by marketers, spammers, scammers, hackers, et. al.
Startpage and IxQuick appear to be from the same folks.
So I have all the trackers blocked as best as possible, Javascript disabled, etc., which makes getting the encrypted URL to work is, well, extra work. Simply copying and pasting the encrypted URL is therefore blocked. I see no value other than shorter typed links in email, forums, newsgroups, etc. to the shortened links, plus making bucks for the folks at TinyURL and others that create them for you. And of course, they are tracking you to.
So, as you may have guessed by now, I do not use Safari. <grin>
I didn't plan on doing it more than once, but had to when you replied. And I've already got too damned many bookmarks.
Dude.
And I'm neither a Dude or Dudette. But been online before there was a world wide web, and a 1200 baud modem was state of the art.
It seems to me that you are suffering from a chronic case of missing-the-point. The first time you clicked that link it was me wasting your time; my bad, but gotcha, laughs all around.
Did not miss the point, and I am not laughing. Wasting the time of your friends is one thing, wasting the time of strangers is simply bad manners.
Any time you clicked it after that you knew what was going to happen, so you were wasting your own time. You're complaining that your time is being wasted because you just won't google it yourself - what am I supposed to do with that except ?
I will plead guilty to assuming that Apple would have documentation on their own website, n'cest-ce pas? (To save you some Googling and unencrypting URLs, http://www.yourdictionary.com/n-est-ce-pas) If Apple had the info on their site, the seach engine would/should have found that link, and I would than have wasted my time with a Google search when it shouldn't have been necessary. I learned a long time ago, to always, always check the mfgr.'s site first for the correct information.

Unable to configure the router.

I bought a router today and I'm having some trouble getting it working. Iinserted the CD and followed the on-screen installation settings including unplugging the modem/router, then plugging it back in, etc. I got to step 11 "Set the Router's Administrative Password" before I had problems. I went to set the password, but I got the message "Unable to configure router. Reset thr router to factory default settings by pressing the reset botton for 5 seconds." I reset the router, but still got the error. Using a quick search I found a similar problem and following the steps on there, pinged 192.168.1.1 with 4 replies. I connected to192.168.1.1 through my browser just fine as well, but I still can't get past step 11.

Have you configured hyour wireless settings on the router and your computer? This has to be done.
For cable go here
Wireless go here.

FF4580 unable to connect Wireless - Windows 8

I have historically used the HP F4580 on XP and Windows 7 but not wirelessly. I have a new PC running Windows 8 64 Bit and am trying to re install the F4580 but would prefer it to run wirelessly.
I have downloaded the software and drivers from the HP website and the printer works fine using a USB connection.
I am trying to convert from USB to wireless using the HP installation and it states my SSID is not available.Even when I type in the SSID it states it is not avaialable. It then tells me the printer I have selected is not connected.
I have added the printer using the mac address to my router as a trusted source.
I have configured the wireless network direct from the device using the wizard and have an IP address for the printer.
The scan print states that wireless is up and running and working ok but I cannot print to it wirelessly. As soon as I remove the USB the printer is unavailable.
I have tried removing the printer and rebooting and reinstalling. I have disabled antivirus and firewalls but still am unable to print wirelessly.
Does anyone have any other ideas or have I missed something really simple.
Thanks
This question was solved.
View Solution.

Hi,
Many thanks to let us know problem solved.
Regards.
BH
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

TS3048 can't scroll up and down with wireless mouse, I have checked setting and everything looks good. Any suggestions on what else I can check?

My wireless mouse has stopped scrolling up and down. I have checked my settings and everything looks good. Any suggestions on what else to check?

Hi:
I wish my suggestion had gotten you further.
I do suggest you try to connect the keyboard again. The request for a number is a step in it trying to pair. If it gets by the number, it sometimes takes a little while to get connected. If you are unable to get it connected and want a new one, I have been using Apple Bluetooth keyboards for years - and I like them. The one I have (the newest model) only uses two batteries and is very thin.
Speaking of batteries, if you are not already doing so, you might consider rechargeables. I have a drawer full of them and use a 15 minute charger. I go tired of buying batteries and rechargeables are environmentally friendly to boot. At the moment, I use 2450 mAh Energizers and a 15 minute Energizer charger (all purchased new on eBay at a very reasonable price).
I am far from an iPad "expert," although I have one. If my suggestion below does not help, post your question in a separate thread in the iPad forum.
I had a terrible time syncing my iCal on my Mac with my iPad iCal (confusing - hopefully it makes sense). I quit using iCloud as that added to the confusion. There is a facility to one-time sync items. When you connect your computer to your iPad, iTunes opens. The system begins a process (automatic backup and so on). After it finishes, you can click on "info." At the bottom of the screen, there is an advanced section. You can select any of the items and then force it to sync. The iCal information from your computer would be deposited on the iPad.
After all that, I do not use a Google calendar so the information may be worthless to you.
If you want to reset the iPad to factory settings, you can do that when it is connected to iTunes (one of the options). Me being me, I try never to erase anything.
Barry
Message was edited by: Barry Hemphill

Wireless mouse pointer which does not move after boot *sometimes*

Hi,
I have a wireless keyboard/mouse combo from Logitech (MK700 keyboard and MX705 mouse), which uses a USB receiver.
After booting, the mouse pointer sometimes is completely blocked, and I have to reboot to make it work. Sometimes I need to do this twice. I cannot reproduce it and this is not linked to the fact the mouse is active or on sleep mode. This seems to be a race condition, considering it is difficult to reproduce. Once the mouse pointer is working, there is no issue anymore during desktop use.
I compared lsmod when mouse pointer is working or not, and did not see any difference in the loaded modules.
This started to happen maybe 3 months ago. I have had this hardware for two years with no problem in the past. It is not a battery problem either.
Has anyone an idea?
Last edited by zebulon (2012-03-21 07:22:53)

Thanks.
Ther is indeed a difference in evedev detection in Xorg logs when mouse is working or not working.
Not working:
[ 22.745]
X.Org X Server 1.12.0
Release Date: 2012-03-04
[ 22.765] X Protocol Version 11, Revision 0
[ 22.765] Build Operating System: Linux 3.2.9-1-ARCH x86_64
[ 22.765] Current Operating System: Linux arch 3.2.12-1-ARCH #1 SMP PREEMPT Mon Mar 19 17:50:01 CET 2012 x86_64
[ 22.765] Kernel command line: root=/dev/sda6 ro vga=891
[ 22.765] Build Date: 05 March 2012 05:59:48AM
[ 22.765]
[ 22.765] Current version of pixman: 0.24.4
[ 22.765] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 22.765] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 22.765] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Mar 23 06:16:55 2012
[ 22.816] (==) Using config file: "/etc/X11/xorg.conf"
[ 22.816] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 22.841] (==) No Layout section. Using the first Screen section.
[ 22.841] (**) |-->Screen "screen1" (0)
[ 22.841] (**) | |-->Monitor "monitor1"
[ 22.841] (**) | |-->Device "device1"
[ 22.841] (**) Option "IgnoreABI" "True"
[ 22.841] (**) Ignoring ABI Version
[ 22.841] (==) Automatically adding devices
[ 22.841] (==) Automatically enabling devices
[ 22.866] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 22.866] Entry deleted from font path.
[ 22.871] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 22.871] Entry deleted from font path.
[ 22.871] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 22.871] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 22.871] Entry deleted from font path.
[ 22.871] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 22.871] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/
[ 22.871] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 22.871] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 22.871] (II) Loader magic: 0x7cef60
[ 22.871] (II) Module ABI versions:
[ 22.871] X.Org ANSI C Emulation: 0.4
[ 22.871] X.Org Video Driver: 12.0
[ 22.871] X.Org XInput driver : 16.0
[ 22.871] X.Org Server Extension : 6.0
[ 22.872] (--) PCI:*(0:1:0:0) 10de:05e2:1682:2394 rev 161, Mem @ 0xf8000000/16777216, 0xe0000000/268435456, 0xf6000000/33554432, I/O @ 0x0000cf00/128, BIOS @ 0x????????/524288
[ 22.872] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 22.872] (WW) "dri" will not be loaded unless you've specified it to be loaded elsewhere.
[ 22.872] (II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
[ 22.872] (II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
[ 22.872] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[ 22.872] (II) "record" will be loaded by default.
[ 22.872] (II) "dri" will be loaded even though the default is to disable it.
[ 22.872] (II) "dri2" will be loaded by default.
[ 22.872] (II) LoadModule: "dbe"
[ 22.948] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 22.955] (II) Module dbe: vendor="X.Org Foundation"
[ 22.955] compiled for 1.12.0, module version = 1.0.0
[ 22.955] Module class: X.Org Server Extension
[ 22.955] ABI class: X.Org Server Extension, version 6.0
[ 22.955] (II) Loading extension DOUBLE-BUFFER
[ 22.955] (II) LoadModule: "v4l"
[ 22.955] (WW) Warning, couldn't open module v4l
[ 22.955] (II) UnloadModule: "v4l"
[ 22.955] (II) Unloading v4l
[ 22.955] (EE) Failed to load module "v4l" (module does not exist, 0)
[ 22.955] (II) LoadModule: "extmod"
[ 22.955] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 22.968] (II) Module extmod: vendor="X.Org Foundation"
[ 22.968] compiled for 1.12.0, module version = 1.0.0
[ 22.968] Module class: X.Org Server Extension
[ 22.968] ABI class: X.Org Server Extension, version 6.0
[ 22.968] (II) Loading extension MIT-SCREEN-SAVER
[ 22.968] (II) Loading extension XFree86-VidModeExtension
[ 22.968] (II) Loading extension XFree86-DGA
[ 22.968] (II) Loading extension DPMS
[ 22.968] (II) Loading extension XVideo
[ 22.968] (II) Loading extension XVideo-MotionCompensation
[ 22.968] (II) Loading extension X-Resource
[ 22.968] (II) LoadModule: "glx"
[ 22.968] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 24.007] (II) Module glx: vendor="NVIDIA Corporation"
[ 24.018] compiled for 4.0.2, module version = 1.0.0
[ 24.018] Module class: X.Org Server Extension
[ 24.018] (II) NVIDIA GLX Module 295.20 Mon Feb 6 21:28:16 PST 2012
[ 24.018] (II) Loading extension GLX
[ 24.018] (II) LoadModule: "record"
[ 24.019] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 24.026] (II) Module record: vendor="X.Org Foundation"
[ 24.026] compiled for 1.12.0, module version = 1.13.0
[ 24.026] Module class: X.Org Server Extension
[ 24.026] ABI class: X.Org Server Extension, version 6.0
[ 24.026] (II) Loading extension RECORD
[ 24.026] (II) LoadModule: "dri2"
[ 24.026] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 24.034] (II) Module dri2: vendor="X.Org Foundation"
[ 24.034] compiled for 1.12.0, module version = 1.2.0
[ 24.034] ABI class: X.Org Server Extension, version 6.0
[ 24.034] (II) Loading extension DRI2
[ 24.034] (II) LoadModule: "nvidia"
[ 24.035] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 24.111] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 24.120] compiled for 4.0.2, module version = 1.0.0
[ 24.120] Module class: X.Org Video Driver
[ 24.154] (II) NVIDIA dlloader X Driver 295.20 Mon Feb 6 21:09:10 PST 2012
[ 24.154] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 24.161] (++) using VT number 7
[ 24.734] (II) Loading sub module "fb"
[ 24.734] (II) LoadModule: "fb"
[ 24.735] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 24.832] (II) Module fb: vendor="X.Org Foundation"
[ 24.832] compiled for 1.12.0, module version = 1.0.0
[ 24.832] ABI class: X.Org ANSI C Emulation, version 0.4
[ 24.832] (II) Loading sub module "wfb"
[ 24.832] (II) LoadModule: "wfb"
[ 24.832] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 27.003] (II) Module wfb: vendor="X.Org Foundation"
[ 27.003] compiled for 1.12.0, module version = 1.0.0
[ 27.003] ABI class: X.Org ANSI C Emulation, version 0.4
[ 27.003] (II) Loading sub module "ramdac"
[ 27.003] (II) LoadModule: "ramdac"
[ 27.003] (II) Module "ramdac" already built-in
[ 29.070] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 29.070] (==) NVIDIA(0): RGB weight 888
[ 29.070] (==) NVIDIA(0): Default visual is TrueColor
[ 29.070] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 29.070] (**) NVIDIA(0): Option "UseEdidDpi" "False"
[ 29.070] (**) NVIDIA(0): Option "DPI" "96 x 96"
[ 29.070] (**) NVIDIA(0): Enabling 2D acceleration
[ 31.411] (II) NVIDIA(GPU-0): Display (SAMSUNG (DFP-1)) does not support NVIDIA 3D Vision
[ 31.411] (II) NVIDIA(GPU-0): stereo.
[ 31.416] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 260 (GT200) at PCI:1:0:0 (GPU-0)
[ 31.416] (--) NVIDIA(0): Memory: 917504 kBytes
[ 31.416] (--) NVIDIA(0): VideoBIOS: 62.00.50.00.52
[ 31.416] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 31.416] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 31.417] (--) NVIDIA(0): Connected display device(s) on GeForce GTX 260 at PCI:1:0:0
[ 31.417] (--) NVIDIA(0): SAMSUNG (DFP-1)
[ 31.417] (--) NVIDIA(0): SAMSUNG (DFP-1): 330.0 MHz maximum pixel clock
[ 31.417] (--) NVIDIA(0): SAMSUNG (DFP-1): Internal Dual Link TMDS
[ 31.503] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 31.503] (**) NVIDIA(0): device SAMSUNG (DFP-1) (Using EDID frequencies has been
[ 31.503] (**) NVIDIA(0): enabled on all display devices.)
[ 31.538] (II) NVIDIA(0): Assigned Display Device: DFP-1
[ 31.538] (WW) NVIDIA(0): No valid modes for "1600x900"; removing.
[ 31.538] (WW) NVIDIA(0): No valid modes for "1366x768"; removing.
[ 31.538] (WW) NVIDIA(0): No valid modes for "1360x765"; removing.
[ 31.538] (II) NVIDIA(0): Validated modes:
[ 31.538] (II) NVIDIA(0): "1920x1080"
[ 31.538] (II) NVIDIA(0): "1280x720"
[ 31.538] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[ 31.566] (**) NVIDIA(0): DPI set to (96, 96); computed from "DPI" X config option
[ 31.566] (--) Depth 24 pixmap format is 32 bpp
[ 31.567] (II) NVIDIA: Using 768.00 MB of virtual memory for indirect memory access.
[ 31.571] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 31.571] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 31.571] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 31.571] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 31.571] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 31.571] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 31.571] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 31.571] (II) NVIDIA(0): Config Options in the README.
[ 31.575] (II) NVIDIA(0): Setting mode "1920x1080"
[ 31.608] (II) Loading extension NV-GLX
[ 31.630] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 31.630] (==) NVIDIA(0): Backing store disabled
[ 31.630] (==) NVIDIA(0): Silken mouse enabled
[ 31.631] (**) NVIDIA(0): DPMS enabled
[ 31.631] (II) Loading extension NV-CONTROL
[ 31.631] (II) Loading extension XINERAMA
[ 31.631] (WW) NVIDIA(0): Option "PreferredMode" is not used
[ 31.631] (II) Loading sub module "dri2"
[ 31.631] (II) LoadModule: "dri2"
[ 31.631] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 31.631] (II) Module dri2: vendor="X.Org Foundation"
[ 31.631] compiled for 1.12.0, module version = 1.2.0
[ 31.631] ABI class: X.Org Server Extension, version 6.0
[ 31.631] (II) NVIDIA(0): [DRI2] Setup complete
[ 31.631] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 31.631] (==) RandR enabled
[ 31.631] (II) Initializing built-in extension Generic Event Extension
[ 31.631] (II) Initializing built-in extension SHAPE
[ 31.631] (II) Initializing built-in extension MIT-SHM
[ 31.631] (II) Initializing built-in extension XInputExtension
[ 31.631] (II) Initializing built-in extension XTEST
[ 31.631] (II) Initializing built-in extension BIG-REQUESTS
[ 31.631] (II) Initializing built-in extension SYNC
[ 31.631] (II) Initializing built-in extension XKEYBOARD
[ 31.631] (II) Initializing built-in extension XC-MISC
[ 31.631] (II) Initializing built-in extension SECURITY
[ 31.631] (II) Initializing built-in extension XINERAMA
[ 31.631] (II) Initializing built-in extension XFIXES
[ 31.631] (II) Initializing built-in extension RENDER
[ 31.631] (II) Initializing built-in extension RANDR
[ 31.631] (II) Initializing built-in extension COMPOSITE
[ 31.631] (II) Initializing built-in extension DAMAGE
[ 31.632] (II) Initializing extension GLX
[ 32.105] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 32.105] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 32.105] (II) LoadModule: "evdev"
[ 32.105] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 32.188] (II) Module evdev: vendor="X.Org Foundation"
[ 32.188] compiled for 1.12.0, module version = 2.7.0
[ 32.188] Module class: X.Org XInput Driver
[ 32.188] ABI class: X.Org XInput driver, version 16.0
[ 32.188] (II) Using input driver 'evdev' for 'Power Button'
[ 32.188] (**) Power Button: always reports core events
[ 32.188] (**) evdev: Power Button: Device: "/dev/input/event2"
[ 32.188] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 32.188] (--) evdev: Power Button: Found keys
[ 32.188] (II) evdev: Power Button: Configuring as keyboard
[ 32.188] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[ 32.188] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 32.188] (**) Option "xkb_rules" "evdev"
[ 32.188] (**) Option "xkb_model" "evdev"
[ 32.188] (**) Option "xkb_layout" "gb"
[ 32.240] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 32.240] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 32.240] (II) Using input driver 'evdev' for 'Power Button'
[ 32.240] (**) Power Button: always reports core events
[ 32.240] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 32.240] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 32.241] (--) evdev: Power Button: Found keys
[ 32.241] (II) evdev: Power Button: Configuring as keyboard
[ 32.241] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1/event1"
[ 32.241] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 32.241] (**) Option "xkb_rules" "evdev"
[ 32.241] (**) Option "xkb_model" "evdev"
[ 32.241] (**) Option "xkb_layout" "gb"
[ 32.241] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:2008 (/dev/input/event0)
[ 32.241] (**) Logitech Unifying Device. Wireless PID:2008: Applying InputClass "evdev keyboard catchall"
[ 32.241] (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:2008'
[ 32.241] (**) Logitech Unifying Device. Wireless PID:2008: always reports core events
[ 32.241] (**) evdev: Logitech Unifying Device. Wireless PID:2008: Device: "/dev/input/event0"
[ 32.241] (--) evdev: Logitech Unifying Device. Wireless PID:2008: Vendor 0x46d Product 0xc52b
[ 32.241] (--) evdev: Logitech Unifying Device. Wireless PID:2008: Found 1 mouse buttons
[ 32.241] (--) evdev: Logitech Unifying Device. Wireless PID:2008: Found scroll wheel(s)
[ 32.241] (--) evdev: Logitech Unifying Device. Wireless PID:2008: Found relative axes
[ 32.241] (II) evdev: Logitech Unifying Device. Wireless PID:2008: Forcing relative x/y axes to exist.
[ 32.241] (--) evdev: Logitech Unifying Device. Wireless PID:2008: Found absolute axes
[ 32.241] (II) evdev: Logitech Unifying Device. Wireless PID:2008: Forcing absolute x/y axes to exist.
[ 32.241] (--) evdev: Logitech Unifying Device. Wireless PID:2008: Found keys
[ 32.241] (II) evdev: Logitech Unifying Device. Wireless PID:2008: Configuring as mouse
[ 32.241] (II) evdev: Logitech Unifying Device. Wireless PID:2008: Configuring as keyboard
[ 32.241] (II) evdev: Logitech Unifying Device. Wireless PID:2008: Adding scrollwheel support
[ 32.241] (**) evdev: Logitech Unifying Device. Wireless PID:2008: YAxisMapping: buttons 4 and 5
[ 32.241] (**) evdev: Logitech Unifying Device. Wireless PID:2008: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 32.241] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.2/0003:046D:C52B.0003/input/input0/event0"
[ 32.241] (II) XINPUT: Adding extended input device "Logitech Unifying Device. Wireless PID:2008" (type: KEYBOARD, id 8)
[ 32.241] (**) Option "xkb_rules" "evdev"
[ 32.241] (**) Option "xkb_model" "evdev"
[ 32.241] (**) Option "xkb_layout" "gb"
[ 32.241] (II) evdev: Logitech Unifying Device. Wireless PID:2008: initialized for relative axes.
[ 32.241] (WW) evdev: Logitech Unifying Device. Wireless PID:2008: ignoring absolute axes.
[ 32.241] (**) Logitech Unifying Device. Wireless PID:2008: (accel) keeping acceleration scheme 1
[ 32.241] (**) Logitech Unifying Device. Wireless PID:2008: (accel) acceleration profile 0
[ 32.241] (**) Logitech Unifying Device. Wireless PID:2008: (accel) acceleration factor: 2.000
[ 32.241] (**) Logitech Unifying Device. Wireless PID:2008: (accel) acceleration threshold: 4
[ 32.241] (II) config/udev: Adding input device UVC Camera (046d:09a4) (/dev/input/event4)
[ 32.241] (**) UVC Camera (046d:09a4): Applying InputClass "evdev keyboard catchall"
[ 32.241] (II) Using input driver 'evdev' for 'UVC Camera (046d:09a4)'
[ 32.241] (**) UVC Camera (046d:09a4): always reports core events
[ 32.241] (**) evdev: UVC Camera (046d:09a4): Device: "/dev/input/event4"
[ 32.241] (--) evdev: UVC Camera (046d:09a4): Vendor 0x46d Product 0x9a4
[ 32.241] (--) evdev: UVC Camera (046d:09a4): Found keys
[ 32.241] (II) evdev: UVC Camera (046d:09a4): Configuring as keyboard
[ 32.242] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-7/2-7:1.0/input/input4/event4"
[ 32.242] (II) XINPUT: Adding extended input device "UVC Camera (046d:09a4)" (type: KEYBOARD, id 9)
[ 32.242] (**) Option "xkb_rules" "evdev"
[ 32.242] (**) Option "xkb_model" "evdev"
[ 32.242] (**) Option "xkb_layout" "gb"
[ 32.242] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
[ 32.242] (II) No input driver specified, ignoring this device.
[ 32.242] (II) This device may have been added with another device file.
Working:
[ 21.623]
X.Org X Server 1.12.0
Release Date: 2012-03-04
[ 21.642] X Protocol Version 11, Revision 0
[ 21.642] Build Operating System: Linux 3.2.9-1-ARCH x86_64
[ 21.642] Current Operating System: Linux arch 3.2.12-1-ARCH #1 SMP PREEMPT Mon Mar 19 17:50:01 CET 2012 x86_64
[ 21.642] Kernel command line: root=/dev/sda6 ro vga=891
[ 21.642] Build Date: 05 March 2012 05:59:48AM
[ 21.642]
[ 21.642] Current version of pixman: 0.24.4
[ 21.642] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 21.642] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 21.643] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Mar 23 06:18:23 2012
[ 21.702] (==) Using config file: "/etc/X11/xorg.conf"
[ 21.702] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 21.727] (==) No Layout section. Using the first Screen section.
[ 21.727] (**) |-->Screen "screen1" (0)
[ 21.727] (**) | |-->Monitor "monitor1"
[ 21.727] (**) | |-->Device "device1"
[ 21.727] (**) Option "IgnoreABI" "True"
[ 21.727] (**) Ignoring ABI Version
[ 21.727] (==) Automatically adding devices
[ 21.727] (==) Automatically enabling devices
[ 21.752] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 21.752] Entry deleted from font path.
[ 21.757] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 21.757] Entry deleted from font path.
[ 21.757] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 21.765] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 21.765] Entry deleted from font path.
[ 21.765] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 21.765] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/
[ 21.765] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 21.765] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 21.765] (II) Loader magic: 0x7cef60
[ 21.765] (II) Module ABI versions:
[ 21.765] X.Org ANSI C Emulation: 0.4
[ 21.765] X.Org Video Driver: 12.0
[ 21.765] X.Org XInput driver : 16.0
[ 21.765] X.Org Server Extension : 6.0
[ 21.766] (--) PCI:*(0:1:0:0) 10de:05e2:1682:2394 rev 161, Mem @ 0xf8000000/16777216, 0xe0000000/268435456, 0xf6000000/33554432, I/O @ 0x0000cf00/128, BIOS @ 0x????????/524288
[ 21.766] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 21.766] (WW) "dri" will not be loaded unless you've specified it to be loaded elsewhere.
[ 21.766] (II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
[ 21.766] (II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
[ 21.766] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[ 21.766] (II) "record" will be loaded by default.
[ 21.766] (II) "dri" will be loaded even though the default is to disable it.
[ 21.766] (II) "dri2" will be loaded by default.
[ 21.766] (II) LoadModule: "dbe"
[ 21.826] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 21.833] (II) Module dbe: vendor="X.Org Foundation"
[ 21.833] compiled for 1.12.0, module version = 1.0.0
[ 21.833] Module class: X.Org Server Extension
[ 21.833] ABI class: X.Org Server Extension, version 6.0
[ 21.833] (II) Loading extension DOUBLE-BUFFER
[ 21.833] (II) LoadModule: "v4l"
[ 21.833] (WW) Warning, couldn't open module v4l
[ 21.833] (II) UnloadModule: "v4l"
[ 21.833] (II) Unloading v4l
[ 21.833] (EE) Failed to load module "v4l" (module does not exist, 0)
[ 21.833] (II) LoadModule: "extmod"
[ 21.833] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 21.846] (II) Module extmod: vendor="X.Org Foundation"
[ 21.846] compiled for 1.12.0, module version = 1.0.0
[ 21.846] Module class: X.Org Server Extension
[ 21.846] ABI class: X.Org Server Extension, version 6.0
[ 21.846] (II) Loading extension MIT-SCREEN-SAVER
[ 21.846] (II) Loading extension XFree86-VidModeExtension
[ 21.846] (II) Loading extension XFree86-DGA
[ 21.846] (II) Loading extension DPMS
[ 21.846] (II) Loading extension XVideo
[ 21.846] (II) Loading extension XVideo-MotionCompensation
[ 21.846] (II) Loading extension X-Resource
[ 21.846] (II) LoadModule: "glx"
[ 21.846] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 22.902] (II) Module glx: vendor="NVIDIA Corporation"
[ 22.913] compiled for 4.0.2, module version = 1.0.0
[ 22.913] Module class: X.Org Server Extension
[ 22.913] (II) NVIDIA GLX Module 295.20 Mon Feb 6 21:28:16 PST 2012
[ 22.913] (II) Loading extension GLX
[ 22.913] (II) LoadModule: "record"
[ 22.913] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 22.921] (II) Module record: vendor="X.Org Foundation"
[ 22.921] compiled for 1.12.0, module version = 1.13.0
[ 22.921] Module class: X.Org Server Extension
[ 22.921] ABI class: X.Org Server Extension, version 6.0
[ 22.921] (II) Loading extension RECORD
[ 22.921] (II) LoadModule: "dri2"
[ 22.921] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 22.929] (II) Module dri2: vendor="X.Org Foundation"
[ 22.929] compiled for 1.12.0, module version = 1.2.0
[ 22.929] ABI class: X.Org Server Extension, version 6.0
[ 22.929] (II) Loading extension DRI2
[ 22.929] (II) LoadModule: "nvidia"
[ 22.929] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 23.006] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 23.014] compiled for 4.0.2, module version = 1.0.0
[ 23.014] Module class: X.Org Video Driver
[ 23.040] (II) NVIDIA dlloader X Driver 295.20 Mon Feb 6 21:09:10 PST 2012
[ 23.040] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 23.047] (++) using VT number 7
[ 23.721] (II) Loading sub module "fb"
[ 23.721] (II) LoadModule: "fb"
[ 23.721] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 24.428] (II) Module fb: vendor="X.Org Foundation"
[ 24.428] compiled for 1.12.0, module version = 1.0.0
[ 24.428] ABI class: X.Org ANSI C Emulation, version 0.4
[ 24.428] (II) Loading sub module "wfb"
[ 24.428] (II) LoadModule: "wfb"
[ 24.428] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 26.531] (II) Module wfb: vendor="X.Org Foundation"
[ 26.531] compiled for 1.12.0, module version = 1.0.0
[ 26.531] ABI class: X.Org ANSI C Emulation, version 0.4
[ 26.531] (II) Loading sub module "ramdac"
[ 26.531] (II) LoadModule: "ramdac"
[ 26.531] (II) Module "ramdac" already built-in
[ 27.811] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 27.811] (==) NVIDIA(0): RGB weight 888
[ 27.811] (==) NVIDIA(0): Default visual is TrueColor
[ 27.811] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 27.811] (**) NVIDIA(0): Option "UseEdidDpi" "False"
[ 27.811] (**) NVIDIA(0): Option "DPI" "96 x 96"
[ 27.811] (**) NVIDIA(0): Enabling 2D acceleration
[ 29.881] (II) NVIDIA(GPU-0): Display (SAMSUNG (DFP-1)) does not support NVIDIA 3D Vision
[ 29.881] (II) NVIDIA(GPU-0): stereo.
[ 29.911] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 260 (GT200) at PCI:1:0:0 (GPU-0)
[ 29.911] (--) NVIDIA(0): Memory: 917504 kBytes
[ 29.911] (--) NVIDIA(0): VideoBIOS: 62.00.50.00.52
[ 29.911] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 29.911] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 29.911] (--) NVIDIA(0): Connected display device(s) on GeForce GTX 260 at PCI:1:0:0
[ 29.911] (--) NVIDIA(0): SAMSUNG (DFP-1)
[ 29.911] (--) NVIDIA(0): SAMSUNG (DFP-1): 330.0 MHz maximum pixel clock
[ 29.911] (--) NVIDIA(0): SAMSUNG (DFP-1): Internal Dual Link TMDS
[ 29.997] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 29.997] (**) NVIDIA(0): device SAMSUNG (DFP-1) (Using EDID frequencies has been
[ 29.997] (**) NVIDIA(0): enabled on all display devices.)
[ 30.033] (II) NVIDIA(0): Assigned Display Device: DFP-1
[ 30.033] (WW) NVIDIA(0): No valid modes for "1600x900"; removing.
[ 30.033] (WW) NVIDIA(0): No valid modes for "1366x768"; removing.
[ 30.033] (WW) NVIDIA(0): No valid modes for "1360x765"; removing.
[ 30.033] (II) NVIDIA(0): Validated modes:
[ 30.033] (II) NVIDIA(0): "1920x1080"
[ 30.033] (II) NVIDIA(0): "1280x720"
[ 30.033] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[ 30.068] (**) NVIDIA(0): DPI set to (96, 96); computed from "DPI" X config option
[ 30.068] (--) Depth 24 pixmap format is 32 bpp
[ 30.068] (II) NVIDIA: Using 768.00 MB of virtual memory for indirect memory access.
[ 30.072] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 30.072] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 30.072] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 30.072] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 30.072] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 30.072] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 30.072] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 30.072] (II) NVIDIA(0): Config Options in the README.
[ 30.076] (II) NVIDIA(0): Setting mode "1920x1080"
[ 30.119] (II) Loading extension NV-GLX
[ 30.149] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 30.149] (==) NVIDIA(0): Backing store disabled
[ 30.149] (==) NVIDIA(0): Silken mouse enabled
[ 30.149] (**) NVIDIA(0): DPMS enabled
[ 30.149] (II) Loading extension NV-CONTROL
[ 30.150] (II) Loading extension XINERAMA
[ 30.150] (WW) NVIDIA(0): Option "PreferredMode" is not used
[ 30.150] (II) Loading sub module "dri2"
[ 30.150] (II) LoadModule: "dri2"
[ 30.150] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 30.150] (II) Module dri2: vendor="X.Org Foundation"
[ 30.150] compiled for 1.12.0, module version = 1.2.0
[ 30.150] ABI class: X.Org Server Extension, version 6.0
[ 30.150] (II) NVIDIA(0): [DRI2] Setup complete
[ 30.150] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 30.150] (==) RandR enabled
[ 30.150] (II) Initializing built-in extension Generic Event Extension
[ 30.150] (II) Initializing built-in extension SHAPE
[ 30.150] (II) Initializing built-in extension MIT-SHM
[ 30.150] (II) Initializing built-in extension XInputExtension
[ 30.150] (II) Initializing built-in extension XTEST
[ 30.150] (II) Initializing built-in extension BIG-REQUESTS
[ 30.150] (II) Initializing built-in extension SYNC
[ 30.150] (II) Initializing built-in extension XKEYBOARD
[ 30.150] (II) Initializing built-in extension XC-MISC
[ 30.150] (II) Initializing built-in extension SECURITY
[ 30.150] (II) Initializing built-in extension XINERAMA
[ 30.150] (II) Initializing built-in extension XFIXES
[ 30.150] (II) Initializing built-in extension RENDER
[ 30.150] (II) Initializing built-in extension RANDR
[ 30.150] (II) Initializing built-in extension COMPOSITE
[ 30.150] (II) Initializing built-in extension DAMAGE
[ 30.151] (II) Initializing extension GLX
[ 30.624] (II) config/udev: Adding input device Power Button (/dev/input/event4)
[ 30.624] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 30.624] (II) LoadModule: "evdev"
[ 30.624] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 30.633] (II) Module evdev: vendor="X.Org Foundation"
[ 30.633] compiled for 1.12.0, module version = 2.7.0
[ 30.633] Module class: X.Org XInput Driver
[ 30.633] ABI class: X.Org XInput driver, version 16.0
[ 30.633] (II) Using input driver 'evdev' for 'Power Button'
[ 30.633] (**) Power Button: always reports core events
[ 30.633] (**) evdev: Power Button: Device: "/dev/input/event4"
[ 30.633] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 30.633] (--) evdev: Power Button: Found keys
[ 30.633] (II) evdev: Power Button: Configuring as keyboard
[ 30.633] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event4"
[ 30.633] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 30.633] (**) Option "xkb_rules" "evdev"
[ 30.633] (**) Option "xkb_model" "evdev"
[ 30.633] (**) Option "xkb_layout" "gb"
[ 30.677] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 30.677] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 30.677] (II) Using input driver 'evdev' for 'Power Button'
[ 30.677] (**) Power Button: always reports core events
[ 30.677] (**) evdev: Power Button: Device: "/dev/input/event3"
[ 30.677] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 30.677] (--) evdev: Power Button: Found keys
[ 30.677] (II) evdev: Power Button: Configuring as keyboard
[ 30.677] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3/event3"
[ 30.677] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 30.677] (**) Option "xkb_rules" "evdev"
[ 30.677] (**) Option "xkb_model" "evdev"
[ 30.677] (**) Option "xkb_layout" "gb"
[ 30.677] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:101b (/dev/input/event0)
[ 30.677] (**) Logitech Unifying Device. Wireless PID:101b: Applying InputClass "evdev pointer catchall"
[ 30.677] (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:101b'
[ 30.677] (**) Logitech Unifying Device. Wireless PID:101b: always reports core events
[ 30.677] (**) evdev: Logitech Unifying Device. Wireless PID:101b: Device: "/dev/input/event0"
[ 30.677] (--) evdev: Logitech Unifying Device. Wireless PID:101b: Vendor 0x46d Product 0xc52b
[ 30.677] (--) evdev: Logitech Unifying Device. Wireless PID:101b: Found 20 mouse buttons
[ 30.677] (--) evdev: Logitech Unifying Device. Wireless PID:101b: Found scroll wheel(s)
[ 30.677] (--) evdev: Logitech Unifying Device. Wireless PID:101b: Found relative axes
[ 30.677] (--) evdev: Logitech Unifying Device. Wireless PID:101b: Found x and y relative axes
[ 30.677] (II) evdev: Logitech Unifying Device. Wireless PID:101b: Configuring as mouse
[ 30.677] (II) evdev: Logitech Unifying Device. Wireless PID:101b: Adding scrollwheel support
[ 30.677] (**) evdev: Logitech Unifying Device. Wireless PID:101b: YAxisMapping: buttons 4 and 5
[ 30.677] (**) evdev: Logitech Unifying Device. Wireless PID:101b: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 30.677] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.2/0003:046D:C52B.0003/input/input0/event0"
[ 30.677] (II) XINPUT: Adding extended input device "Logitech Unifying Device. Wireless PID:101b" (type: MOUSE, id 8)
[ 30.677] (II) evdev: Logitech Unifying Device. Wireless PID:101b: initialized for relative axes.
[ 30.677] (**) Logitech Unifying Device. Wireless PID:101b: (accel) keeping acceleration scheme 1
[ 30.677] (**) Logitech Unifying Device. Wireless PID:101b: (accel) acceleration profile 0
[ 30.677] (**) Logitech Unifying Device. Wireless PID:101b: (accel) acceleration factor: 2.000
[ 30.677] (**) Logitech Unifying Device. Wireless PID:101b: (accel) acceleration threshold: 4
[ 30.677] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:101b (/dev/input/mouse0)
[ 30.677] (II) No input driver specified, ignoring this device.
[ 30.677] (II) This device may have been added with another device file.
[ 30.678] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:2008 (/dev/input/event1)
[ 30.678] (**) Logitech Unifying Device. Wireless PID:2008: Applying InputClass "evdev keyboard catchall"
[ 30.678] (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:2008'
[ 30.678] (**) Logitech Unifying Device. Wireless PID:2008: always reports core events
[ 30.678] (**) evdev: Logitech Unifying Device. Wireless PID:2008: Device: "/dev/input/event1"
[ 30.678] (--) evdev: Logitech Unifying Device. Wireless PID:2008: Vendor 0x46d Product 0xc52b
[ 30.678] (--) evdev: Logitech Unifying Device. Wireless PID:2008: Found 1 mouse buttons
[ 30.678] (--) evdev: Logitech Unifying Device. Wireless PID:2008: Found scroll wheel(s)
[ 30.678] (--) evdev: Logitech Unifying Device. Wireless PID:2008: Found relative axes
[ 30.678] (II) evdev: Logitech Unifying Device. Wireless PID:2008: Forcing relative x/y axes to exist.
[ 30.678] (--) evdev: Logitech Unifying Device. Wireless PID:2008: Found absolute axes
[ 30.678] (II) evdev: Logitech Unifying Device. Wireless PID:2008: Forcing absolute x/y axes to exist.
[ 30.678] (--) evdev: Logitech Unifying Device. Wireless PID:2008: Found keys
[ 30.678] (II) evdev: Logitech Unifying Device. Wireless PID:2008: Configuring as mouse
[ 30.678] (II) evdev: Logitech Unifying Device. Wireless PID:2008: Configuring as keyboard
[ 30.678] (II) evdev: Logitech Unifying Device. Wireless PID:2008: Adding scrollwheel support
[ 30.678] (**) evdev: Logitech Unifying Device. Wireless PID:2008: YAxisMapping: buttons 4 and 5
[ 30.678] (**) evdev: Logitech Unifying Device. Wireless PID:2008: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 30.678] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.2/0003:046D:C52B.0003/input/input1/event1"
[ 30.678] (II) XINPUT: Adding extended input device "Logitech Unifying Device. Wireless PID:2008" (type: KEYBOARD, id 9)
[ 30.678] (**) Option "xkb_rules" "evdev"
[ 30.678] (**) Option "xkb_model" "evdev"
[ 30.678] (**) Option "xkb_layout" "gb"
[ 30.678] (II) evdev: Logitech Unifying Device. Wireless PID:2008: initialized for relative axes.
[ 30.678] (WW) evdev: Logitech Unifying Device. Wireless PID:2008: ignoring absolute axes.
[ 30.678] (**) Logitech Unifying Device. Wireless PID:2008: (accel) keeping acceleration scheme 1
[ 30.678] (**) Logitech Unifying Device. Wireless PID:2008: (accel) acceleration profile 0
[ 30.678] (**) Logitech Unifying Device. Wireless PID:2008: (accel) acceleration factor: 2.000
[ 30.678] (**) Logitech Unifying Device. Wireless PID:2008: (accel) acceleration threshold: 4
[ 30.678] (II) config/udev: Adding input device UVC Camera (046d:09a4) (/dev/input/event5)
[ 30.678] (**) UVC Camera (046d:09a4): Applying InputClass "evdev keyboard catchall"
[ 30.678] (II) Using input driver 'evdev' for 'UVC Camera (046d:09a4)'
[ 30.678] (**) UVC Camera (046d:09a4): always reports core events
[ 30.678] (**) evdev: UVC Camera (046d:09a4): Device: "/dev/input/event5"
[ 30.678] (--) evdev: UVC Camera (046d:09a4): Vendor 0x46d Product 0x9a4
[ 30.678] (--) evdev: UVC Camera (046d:09a4): Found keys
[ 30.678] (II) evdev: UVC Camera (046d:09a4): Configuring as keyboard
[ 30.678] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-7/2-7:1.0/input/input5/event5"
[ 30.678] (II) XINPUT: Adding extended input device "UVC Camera (046d:09a4)" (type: KEYBOARD, id 10)
[ 30.678] (**) Option "xkb_rules" "evdev"
[ 30.678] (**) Option "xkb_model" "evdev"
[ 30.678] (**) Option "xkb_layout" "gb"
[ 30.678] (II) config/udev: Adding input device PC Speaker (/dev/input/event2)
[ 30.678] (II) No input driver specified, ignoring this device.
[ 30.678] (II) This device may have been added with another device file.
I note the differences start there:
(--) evdev: Logitech Unifying Device. Wireless PID:101b: Found x and y relative axes
vs
(II) evdev: Logitech Unifying Device. Wireless PID:2008: Forcing relative x/y axes to exist.
Could my Logitech camera interfere with the keyboard/mouse unifier detection?

Wireless Mouse X3300 - Software Suite Install

Recently got a new Hp Wireless mouse x3300.
It works fine (Windows 7 recognised it as a new input devise) but would like to be able to configure it.
Downloaded the latest drivers and software suite from the HP site (sp60614.exe).
But these fail to install correctly and come up with permission issues on trying to create registry keys.
Error 1401 - Could not create key \SOFTWARE\Microsift\Windows\CurrentVersion\Run.
I've tried installing both as me and as administrator but makes no difference.
Other people seem to have reported this issue but I've seen no solution.
Can you help?!
I'm running standard Microsoft Windows 7 Home Premium (64 bit)
I've also had a look at the regsitry permisiions for that key and can see no obvious permisision issue.

Amy, welcome to the forum.
Here is the Quick Start page for the mouse. Click on the link "http://h10025.www1.hp.com/ewfrf/wc/supportLanding?cc=us&lc=en" and choose your country. From there you should be able to find the software and driver for the mouse.
Please click the "Thumbs Up+ button" if I have helped you and click "Accept as Solution" if your problem is solved.
Signature:
HP TouchPad - 1.2 GHz; 1 GB memory; 32 GB storage; WebOS/CyanogenMod 11(Kit Kat)
HP 10 Plus; Android-Kit Kat; 1.0 GHz Allwinner A31 ARM Cortex A7 Quad Core Processor ; 2GB RAM Memory Long: 2 GB DDR3L SDRAM (1600MHz); 16GB disable eMMC 16GB v4.51
HP Omen; i7-4710QH; 8 GB memory; 256 GB San Disk SSD; Win 8.1
HP Photosmart 7520 AIO
++++++++++++++++++
**Click the Thumbs Up+ to say 'Thanks' and the 'Accept as Solution' if I have solved your problem.**
Intelligence is God given; Wisdom is the sum of our mistakes!
I am not an HP employee.

Unable to connect wirelessly to BTHome Hub

I have a ibook G4 running OSX 10.3.9 fitted out with Airport and have recently taken delivery of a BTHomehub, Both my Mac and laptop PC (also fitted out with wireless capability) are unable to connect wirelessly to this Hub despite being able to connect to the NET using an ethernet cable. It appears that there is no wireless signal being transmitted from the Hub, or at least a signal the both computers can recognise. We have contacted the support teams who have been unable to resolve the issue, and have replaced the Hub, guess what same problem.
Has anyone had similar experiences and if so how was it resolved? There doesn't appear to be any real info on the web about this.
ibook G4 Mac OS X (10.3.9)

Duane, The BtHomeHub is a UK device, both the Mac and the PC were purchased and are used in the UK. The hub is configured to detect settings automatically although i have tried all the different channels manually, no joy.
Anyone got any experience of this device or ways to resolve the problem?

Unable to configure wireless mouse

Similar Messages

Maybe you are looking for