Wireless Keyboard not working with Tungsten T5

I recently purchased a Universal Wireless Keyboard that I'd hoped to use with my Tunsten T5 while on a trip. Unfortunately, I wasn't able to get it working before I left. Now I'm back and want to try again, but need some help.
I'm running Vista on my PC, so the software that came on the install CD with the keyboard wouldn't work. I checked online and downloaded what I thought was the proper file and it seemed to install fine when I synced, but when I turn the keyboard on and place the T5 in it's cradle, nothing happens. And, yes, I've careful to position the wand over the top of the device where the infrared port is.
Any thoughts or suggestions?
Post relates to: Tungsten T5

I don't see a way to turn on the application on the T5. When I run the Keyboard application, I just get a screen where I can set the Key Repeat Rate, the Delay Until Repeat interval, a place to test Repeat Settings, and check boxes to enable key clicks and the keyboard. If I enable the keyboard (is that "turning it on") and go into Documents to Go, then the keyboard doesn't work and when I go back into the Keyboard application, the enabling checkbox is no longer checked.
I also don't see a way to enable Infrared. If I look under Connections, there are choices to enable IR to a PC/Handheld and several other devices, like a Universal Drive. But there's no choice for a Wireless Keyboard. If I look under Power, Beam Receive is ON.
Post relates to: Tungsten T5

Similar Messages

Wireless keyboard not working with Boot Camp

I have a brand new 15" Macbook Pro. I need to run Windows for work so I installed Boot Camp and Windows 8.1. I have a HP wireless keyboard with a USB dongle. It will not work at all. Windows recognizes that I've plugged in the dongle but the keyboard won't work at all. It's a brand-new keyboard and the batteries show full charge. All drivers look good in device manager. When I went thru the Windows troubleshooter, which is typically worthless, it said something about the dongle being USB 2.0 and the Mac's USB is 3.0. But shouldn't it be backward compatible? It has no problem with my old wireless mouse with a USB dongle.
I also notice a significant difference in the clarity on my dual external monitors with Windows instead of OSx. The colors aren't as sharp and the text isn't as clear - kind of fuzzy. Is that just how it goes with boot camp, or is there anything I can do, like maybe an upgraded driver, to get the same clarity on my dual monitors with Windows like I get with OSx?
Any help is appreciated.

Unfortunately I can't turn off Bluetooth in Win 8.1. I go to the page where i should see the slider and the page just spins and spins. I thought my install might be hosed so I blew it away and did a fresh boot camp install. Still no joy; BT still spins - and I still can't connect to the USB keyboard. I can plug the dongle in and see it in devices, and it says it's ready to go but the keyboard doesn't work. It's brand-new and has worked on a Windows box so I know it's not a bad keyboard. Maybe time to go back to a Windows box and ditch boot camp?

Wireless Keyboard not working with iPad2

I've already wasted way too much time on a Apple product that has changed my mind about the company. I jumped through all of the necessary hoops to engage my wireless keyboard with my iPad2 but the keyboard will not type a single word. It says it's connected but it's not working. I got it to type twice for about 5 seconds each time but that was it. If anyone has any suggestions I'm all ears. I hope there is a simple fix.

The key lag or delay seems like it's a setting in the keyboard settings/ipad keyboard settings itself. Witness the keyboard preference pane in mac os x. I wonder if it's a accessibility setting...
To rule out third party apps:
1. Launch the Notes app. Type. If the notes app does not have the issue, it is the specific third-party apps you are using. I notice that some apps do not support bluetooth keyboards. Normally, they don't type at all.
But who knows?
2. Look for something in setting that controls keyboard delay?
Shut down any "open" apps. (I know that multiple apps cannot run at the same time on the ipad, but humor me.) [Note: just replicating what apple sometimes has people try.]
Turn off wi-fi and cellular data. Test again.
If this works, some syncing or downloading activity is happening in the background and creating lag.
Given that entering the code works fine, I doubt the hardware or bluetooth connection is faulty.
Post back with results and we'll decide what to do.
P.S Have you tried pairing the keyboard to a computer? Does this work ok?

Why is Emoji Keyboard not working with iOS7....??? Is there any setting which I am missing? Can anyone help

Why is Emoji Keyboard not working with iOS7....??? Is there any setting which I am missing? Can anyone help

Yes. you should keep your media in iTunes, and indeed you should also keep a backup of your library as well. if you have the device set up for manual management then the content would remain on it when deleted from the library, but you would have no way to restore the device if there was a problem.
See also: Getting iTunes & Windows Media Player to play nicely
tt2

White A1016 wireless keyboard not pairing with new MacBook Pro

I still have (and love) the original white bluetooth Mac keyboard (model A1016, with numeric keypad and function keys). It won't pair to my new MacBook Pro. It's discoverable, appears in the list, I can select it and try to pair. Then it sits with the spinning wheel for some time before giving up.
Oddly, if I press "return" during the spinning, it (very) briefly displays the passcode, but of course by then it's too late, and fails saying that I got the passcode wrong!
This appears to be a Bluetooth system preference problem - is anyone else seeing this?
This Apple technote suggests that this keyboard should work with iOS, whereas the original aluminium one doesn't (although it's not entirely clear)... if it works with iOS, I can't see why it won't work with OS X 10.8.4!

My old Bluetooth Mighty Mouse won't work with my newer MBP running Mountain Lion, either. I suspect that the keyboard is incompatible with your new machine/OS X 10.8.x.
Clinton

APPLE mouse & keyboard not working with Windows (Bootcamp)

I installed Leopard and Windows XP on my Mac Pro. The installation went very smoothly. Only problem I have is that my Apple wireless keyboard and mouse do not work on Windows (frozen) although they work fine on Leopard. I tried a Logitech wireless trackball and it works fine on both Windows and Leopard. Any suggestion?

Thanks. I upgraded from Tiger and downloaded Bootcamp from Leopard Installation disc ( I did not have a beta version ). I then installed Windows XP SP2 ( brand new, just bought for that purpose ). Wonder if Mac wireless keyboard and mouse are compatible with Window. Everything else work beyond my expectation.

Apple Bluetooth Keyboard not working with Macbook??

I copied this from a post on a reply earlier, but thought I'd start a new post and hope that someone has had a similar problem.
I have the new Apple wireless keyboard that doesn't work on my Macbook. Ironically, the only keys that do work are the top row. Screen brighten or dim, Dashboard, speaker volume control etc...
I've connected it and paired it successfully, but the keys just don't seem to work. (delete and arrow keys also work) After a while, my mighty mouse (wireless) start acting funny, or the track pad button on the laptop itself stops working. Shutting of the keyboard at this point doesn't help and I need to reboot the computer.
I've taken it to Fortune Tower in Bangkok where they have a apple support center and he couldn't get it to work on his 17" mac book pro either. He wanted me to leave it, but I took it back to the international departure terminal of the Bangkok international airport, (had to wait for another flight to China to do this) and returned it to the store where I bought it. But they wanted to see the problem and I showed them that it didn't work. Convinced, then then brought out a new one and I wanted to verify that IT worked but same exact problems.
I suggested that they connect it to another computer? Which they did, an Imac and it worked fine. Then they connected it to a Mac Book Pro, (15 inch) and it worked fine there as well.
Could this be a firmware update issue?
Anyone else having problems like this?
I just hope that this isn't a simple setting somewhere that I've overlooked... but I'll try anything at this point.
thanks,

I have exactly the same problem! Macbook Pro 2GHz (so not a very recent one...), OS, firmware, etc updated to the latest. My Mac dealer proposed to do a clean installation of 10.5.2 - did not help. Apple Support told me to uninstall the keyboard and install it again (for more help they want money...) I did - same problem. Only function keys and cursor keys work. Funny thing - during pairing the code can be entered and recognized, but later no character cames through.
The keyboard is perfectly OK, since it works with my MacPro without any problems.
The mouse, on other hand, works nicely so far.
Maybe now will someone give us a wise advice?

Aluminum Wireless Keyboard not working properly after Firmware update 1.1

Hi,
Well, as the subject says, my keyboard is not working properly after I updated the firmware. The problem is that several keys (delete, down arrow, brackets and apostrophe) stopped working right after I installed the update. I never dropped it or hit it. And I did not stop or interrupt or did anything during the install. I take very good care of it.
I have already tried toubleshooting with the support page, restarting the iMac, taking off the batteries, setting it up with bluetooth again, going back a week with time machine and to reinstall the firmware. So, if you have something new for me to try, I will really apreciate it.
Thanks in advance.
Franco.

I have 24" iMac with the Apple wireless M&KB - I know this is basic but have you tried a fresh set of batteries? My KB will refuse to establish connection when batteries are on the weak side the firmware update may just be a co incidents. If your wireless mouse is working OK then I would guess the blue tooth is functioning.
Not sure about the 10.49 download - are your other file downloads completing properly? Are there any error messages?
Steve

F# keys on Apple Wireless Keyboard not working correctly.

Hello everyone,
Today I bought a brand new Apple Wireless Keyboard (the small ones who resemble laptop keyboards), which I'm very glad I bought as some keys on my older keyboard started not working anymore.
I configured the keyboard with bluetooth and it's working just fine, except for one thing:
The F# keys don't work as their respective icons indicate (i.e. If I press F10, F11 and/or F12, the volume isn't affected as it normally should, but instead the keys don't seem to respond, as if I weren't pressing them).
In the Keyboard & Mouse panel in System Preferences, under the Keyboard Shortcuts, I managed to reset the F1 to F4 keys so they work as their respective icons indicate, though I didn't find and don't know how to create any shortcuts to make the volume keys (F10, F11 & F12) work again.
Also, I would appreciate if you could help me out to reset the F7, F8 & F9 keys, which don't work either.
I tried checking and un-checking the "Use the keys F1, F2 and so on, as standard function keys." option under the Keyboard tab, and pressing the "fn" key while pressing the F# keys, but none of those attempts seem to change anything to how the F# keys work.
I don't know what else to do anymore and I would really appreciate some help now.
Thanks in advance for your responses,
Oscar.

Shutdown your macbook.After thats done , switch the wireless keyboard off. Press Shift + Ctrl + Option + Power Key (all together ) and then release together. Start up the macbook and once that's up start up the keyboard.Try now.The keys should work fine.

Magic mouse and aluminum wireless keyboard not working in windows 7

Aluminum wireless keyboard (fully upgraded firmware as of 2/19/2010) not working, or magic mouse. Both from Apple Store, not amazon or ebay.
No error shown for magic mouse, only "connecting to device" for 15 minutes now.
With keyboard, at times it shows an error, but sometimes it lets me type a passkey. It doesn't recognize the passkey although it's saying it's paired, it doesn't work.
Help?

Getting Bluetooth set up initially in Bootcamp is a bit of a hit and miss affair in my experience, but persistence pays off, and connection is reliable. I gave up with the keyboard on my Mac Pro at one stage, tried again a few days later and it worked.
How did you do it?
Persistence and repetition, reading lots of threads and getting snippets from various sources, can't recall any silver bullets.
Have you searched this forum, there are a LOT of posts on the subject.
Links please? I can't find any.
If you type "bluetooth" in the search box while at the top level of the Bootcamp section you will get six pages of hits. Here are just a few, not necessarily the best or a complete list or in any particular order, but they contain relevant info.
I can't remember the detail now but one of the key steps for me was launching the bluetooth "service" mentioned in some of these links. Initially option wasn't appearing at all. Also mine (and others) seems to need a single click after boot to be activated. If you try and move it before a click it won't respond so you might think it wasn't working.
BTW I am assuming you have successfully installed the Boot Camp 3.1 drivers?
http://discussions.apple.com/thread.jspa?threadID=2221427&start=0&tstart=0
http://discussions.apple.com/message.jspa?messageID=10943844#10943844
http://discussions.apple.com/thread.jspa?messageID=10669525&#10669525
http://discussions.apple.com/thread.jspa?threadID=2057008&tstart=0
http://discussions.apple.com/thread.jspa?messageID=10948512&#10948512
http://discussions.apple.com/thread.jspa?messageID=10935130&#10935130
I am afraid at this point I stopped trawling through looking for the most relevant ones so the above is incomplete.

Slim Wireless Keyboard Not Working (Boot-Camp (Windows XP SP2) Leopard

I installed Boot Camp with Windows XP SP2 on my iMac. My new slim apple wireless keyboard did not after I rebooted to finish the install. It worked when I was installing it though. My wireless mighty mouse works fine with xp.I have given my keyboard many passkeys in the bluetooth settings on windows, but it still doesn't work. I have Mac OS X Leopard. My boot camp version is 2.0. I have also tried to repair the drivers with the boot camp drivers on the leopard disk but that was unsucessful.
Help Soon, Thanks

I tried what Snackyotter did with no success. I don't really use the Caps Lock Key, or the Option Key at boot, when I want to switch to Boot-Camp and Mac OS X I just change the Boot Disk in System Preferences & vise-versa. Thanks for trying to help though. This weekend I am returning my Apple Slim Wireless Keyboard at the Apple Store. I still have the original packaging and receipt, I bought it offline and received it a few days ago. If the return doesn't go as planned and I'm stuck with this keyboard I will keep this question labeled 'unanswered'. If the return does go well I will label it solved, there is no need really to keep this topic waving around when I no longer have the Apple Wireless Keyboard. I have never EVER even thought of returning an Apple product before, wish me luck. To Apple though I must say that I am disappointed that you have had many months to fix this simple issue since this keyboard came out, but have decided not to. I will try to keep you updated. Again Thank You for your kind support.
tmt345

Key on wireless keyboard not working

I've noticed that if I use Pages or MS Word for Mac, my Apple Wireless Keyboard no longer allows me to use the apostrophe/quotes key. Very strange. Initially I thought the keyboard might be faulty, but noticed at the bottom of MS Word there is a "Spelling and Grammar" box which dynamically updates to show progress with an input device (like the keyboard). I get very clear feedback from this that tapping the key is noted by the computer...yet no apostrophe or quotes show on the page.
Similary, when I tap the key using Pages, the cursor jiggles slightly, but no letter is shown. More confusing is that when I tap the apostrophe in Safari (as I did in entering the word "I've" at the start of this note) the apostrophe/quotes key works.
Any suggestion on how to fix? As you can imagine, trying to type a document without these is challenging. Thanks in advance for any suggestions.

Just found the problem: have been using the font "Garamond" which, in this incarnation (and bizarrely) doesn't have the apostrophe or quotation mark in it. Changing to another font fixed this.

A1255 Wireless keyboard not pairing with macbook pro 10.6.5

Trying to pair my wireless keyboard with macbook pro but it's not pairing.
What i did is :
System Preference -> Keyboard -> set up bluetooth wirless keyboard
my keyboard appears for a moment and the i goes off.
it says 1 keyboard found then keep searching and suddenly no keyboard found.
Any help is appreciated.
Cheers

Hello H:
These forums are not chat rooms, but since you used my name I will address your post.
Do you work for Apple?
No. These are user-to-user forums. The forums are moderated by Apple, but do not represent official responses from the company. If an Apple employee would post here (very rare), they would have either a purple apple (forum host) or a silver apple (employee) under their name.
Every post about this issue, going back to early 2009 you have made the SAME suggestion. It doesn't work.
That statement is inaccurate. If you read the posts carefully, I do not cut/paste the same suggestion to address issues. However, trying to address issues without hands-on access to devices necessarily requires one to suggest solutions that have worked in similar situations. Bluetooth issues are not rocket science and there are only a few things that are available to resolve problems. If you look at the little blue bars next to my name that represent user +"thank yous+" for suggestions that worked, I must have made a few suggestions that did work.
Like everyone else that tries to help others here, we are unpaid volunteers. If you have better sources to obtain information, I certainly recommend that you seek those sources out. If you have issues with Apple, take them up with the company. Ranting here about your particular problem is not helping anyone.
Barry

Wireless keyboard not pairing with IMac while mouse

I am having trouble with the wireless keyboard entering my password when booting up. It will not let me enter any characters. My wireless mouse & trackpad seem to work fine. Right now I am submitting this issue through my Ipad (3rd Gen) using the same keyboard that will not pair with my IMac. I called Apple tech yesterday and he had me remove the new batteries from the keyboard and depress the power button for one minute, then replace the batteries and power up the Imac. That solution seemed to work yesterday. Last evening i shut the machine down and tried to start today and had the same issue. The keyboard is working fine with this Ipad and had no trouble recognizing it on bluetooth. Has anybody had this same problem, I was considering purchasing a USB apple keyboard until I tried the keyboard with a different device (my ipad)

How did you get on? My brother is having a similar problem, he bought a replacement wireless keyboard which is not recognized by/paired with his iMac and thus he can't login..

Keyboard not working with xorg-server 1.6.1-1 or xkeyboard 1.5-1

Hello!
I have a problem with a no working keyboard. It seems like this is a problem related to some of the latest xkeyboard-config or xorg-server versions. This have been a problem some time, but it have been solved by downgrading xkeyboard-config to v1.5-1 and xorg-server to v1.6.1-1.
I'm booting into runlevel 3. Keyboard is working in the terminal, but when I run startx, the keyboard stops working. The mouse works fine.
Have tested with an empty xorg.conf file. Then I get a 'no screen found' error. And I have tryed to enable the keyboard entry in xorg.conf. X starts, but no keyboard. Hal is running.
Any ideas?
The xorg.conf and rc.conf
# Copyright 2004 The X.Org Foundation
Section "ServerLayout"
Identifier "Laptop"
Screen 0 "Default" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
# InputDevice "EvdevMouse" "CorePointer"
# Inputdevice "Trackpoint" "SendCoreEvents"
EndSection
Section "ServerFlags"
Option "AutoAddDevices" "True"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
EndSection
Section "Monitor"
Identifier "LCD"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "radeon_hd"
Driver "fglrx"
EndSection
Section "Screen"
Identifier "Default"
Device "radeon_hd"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1440x900" "1024x768"
Virtual 2720 1024
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection
# /etc/rc.conf - Main Configuration for Arch Linux
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="Europe/Oslo"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
MOD_AUTOLOAD="yes"
MODULES=(fglrx vboxdrv vboxnetadp acpi_cpufreq cpufreq_ondemand !pcspkr)
USELVM="no"
HOSTNAME="ArchT400"
eth0="dhcp"
INTERFACES=(!eth0)
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
DAEMONS=(syslog-ng network netfs hal laptop-mode cpufreq crond oss @autowifi @cups @openntpd @hddtemp)
Last edited by orjanp (2009-08-11 13:07:41)

Her er Xorg.0.log
X.Org X Server 1.6.3
Release Date: 2009-7-31
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.30-ARCH x86_64
Current Operating System: Linux ArchT400 2.6.30-ARCH #1 SMP PREEMPT Fri Jul 31 07:30:28 CEST 2009 x86_64
Build Date: 03 August 2009 08:17:16PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Aug 12 10:39:18 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Laptop"
(**) |-->Screen "Default" (0)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "radeon_hd"
(==) No monitor specified for screen "Default".
Using a default monitor configuration.
(**) Option "AutoAddDevices" "True"
(**) Automatically adding devices
(==) Automatically enabling devices
(==) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1,
built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable AllowEmptyInput.
(II) Loader magic: 0x7540
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(--) using VT number 7
(--) PCI:*(0:1:0:0) 1002:95c4:17aa:210e ATI Technologies Inc Mobility Radeon HD 3400 Series rev 0, Mem @ 0xd0000000/268435456, 0xcfff0000/65536, I/O @ 0x00002000/256, BIOS @ 0x????????/131072
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.6.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.6.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="FireGL - ATI Technologies Inc."
compiled for 7.4.0, module version = 1.0.0
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.6.3, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 7.4.0, module version = 1.0.0
(II) Loading extension XFree86-DRI
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Loading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
compiled for 1.4.99.906, module version = 8.63.2
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.6.3, module version = 1.1.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "fglrx"
(II) Loading /usr/lib/xorg/modules/drivers//fglrx_drv.so
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
compiled for 1.4.99.906, module version = 8.63.2
Module class: X.Org Video Driver
(II) Primary Device is: PCI 01@00:00:0
(WW) Falling back to old probe method for fglrx
(II) ATI Proprietary Linux Driver Version Identifier:8.63.2
(II) ATI Proprietary Linux Driver Release Identifier: 8.632
(II) ATI Proprietary Linux Driver Build Date: Jul 2 2009 12:25:51
(II) Loading PCS database from /etc/ati/amdpcsdb
(WW) This ATI Proprietary Linux Driver does not guarantee support of video driver ABI higher than 2.0
(WW) Video driver ABI version of the X server is 5.0
(--) Assigning device section with no busID to primary device
(--) Chipset Supported AMD Graphics Processor (0x95C4) found
(II) AMD Video driver is running on a device belonging to a group targeted for this release
(II) AMD Video driver is signed
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) fglrx(0): pEnt->device->identifier=0x154b6d0
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
[5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
[6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
[7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
[10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
(II) Setting vga for screen 0.
(II) fglrx(0): === [atiddxPreInit] === begin
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 1.6.3, module version = 0.1.0
ABI class: X.Org Video Driver, version 5.0
(II) fglrx(0): PCI bus 1 card 0 func 0
(**) fglrx(0): Depth 24, (--) framebuffer bpp 32
(II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) fglrx(0): Default visual is TrueColor
(II) fglrx(0): 10BitPixelFormat disabled by default
(==) fglrx(0): RGB weight 888
(II) fglrx(0): Using 8 bits per RGB (8 bit DAC)
(==) fglrx(0): Gamma Correction for I is 0x06419064
(==) fglrx(0): Gamma Correction for II is 0x06419064
(==) fglrx(0): Buffer Tiling is ON
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Reloading /usr/lib/xorg/modules/linux//libfglrxdrm.so
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: drmOpenMinor returns 8
drmOpenByBusid: drmGetBusid reports PCI:1:0:0
(--) fglrx(0): Chipset: "ATI Mobility Radeon HD 3400 Series" (Chipset = 0x95c4)
(--) fglrx(0): (PciSubVendor = 0x17aa, PciSubDevice = 0x210e)
(--) fglrx(0): board vendor info: third party graphics adapter - NOT original ATI
(--) fglrx(0): Linear framebuffer (phys) at 0xd0000000
(--) fglrx(0): MMIO registers at 0xcfff0000
(--) fglrx(0): I/O port at 0x00002000
(==) fglrx(0): ROM-BIOS at 0x000c0000
(II) fglrx(0): Battery is used
(II) fglrx(0): Primary V_BIOS segment is: 0xc000
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 1.6.3, module version = 1.1.0
ABI class: X.Org Video Driver, version 5.0
(II) fglrx(0): VESA BIOS detected
(II) fglrx(0): VESA VBE Version 3.0
(II) fglrx(0): VESA VBE Total Mem: 16384 kB
(II) fglrx(0): VESA VBE OEM: ATI ATOMBIOS
(II) fglrx(0): VESA VBE OEM Software Rev: 10.88
(II) fglrx(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies Inc.
(II) fglrx(0): VESA VBE OEM Product: M82
(II) fglrx(0): VESA VBE OEM Product Rev: 01.00
(II) fglrx(0): ATI Video BIOS revision 9 or later detected
(--) fglrx(0): Video RAM: 262144 kByte, Type: DDR3
(II) fglrx(0): PCIE card detected
(--) fglrx(0): Using per-process page tables (PPPT) as GART.
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(II) fglrx(0): Using adapter: 1:0.0.
(II) fglrx(0): [FB] MC range(MCFBBase = 0xc0000000, MCFBSize = 0x10000000)
(II) fglrx(0): [pcie] 1986048 kB allocated
(II) fglrx(0): [drm] DRM buffer queue setup: nbufs = 100 bufsize = 65536
(II) fglrx(0): Interrupt handler installed at IRQ 32.
(II) fglrx(0): IRQ 32 Enabled.
(II) fglrx(0): RandR 1.2 support is enabled!
(II) fglrx(0): RandR 1.2 rotation support is enabled!
(==) fglrx(0): Center Mode is disabled
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.6.3, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) fglrx(0): ***Display: ConnectedDisplayTypes=0x00000002, disabled=0x00000000
(II) fglrx(0): Connected Display1: LCD on internal LVDS [lvds]
(II) fglrx(0): Display1 EDID data ---------------------------
(II) fglrx(0): Manufacturer: LEN Model: 4036 Serial#: 0
(II) fglrx(0): Year: 2008 Week: 0
(II) fglrx(0): EDID Version: 1.3
(II) fglrx(0): Digital Display Input
(II) fglrx(0): Max Image Size [cm]: horiz.: 30 vert.: 19
(II) fglrx(0): Gamma: 2.20
(II) fglrx(0): DPMS capabilities: StandBy Suspend Off
(II) fglrx(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
(II) fglrx(0): First detailed timing is preferred mode
(II) fglrx(0): redX: 0.571 redY: 0.340 greenX: 0.338 greenY: 0.542
(II) fglrx(0): blueX: 0.158 blueY: 0.125 whiteX: 0.313 whiteY: 0.329
(II) fglrx(0): Manufacturer's mask: 0
(II) fglrx(0): Supported detailed timing:
(II) fglrx(0): clock: 101.6 MHz Image Size: 304 x 190 mm
(II) fglrx(0): h_active: 1440 h_sync: 1488 h_sync_end 1520 h_blank_end 1824 h_border: 0
(II) fglrx(0): v_active: 900 v_sync: 903 v_sync_end 909 v_blanking: 926 v_border: 0
(II) fglrx(0): Supported detailed timing:
(II) fglrx(0): clock: 85.6 MHz Image Size: 304 x 190 mm
(II) fglrx(0): h_active: 1440 h_sync: 1488 h_sync_end 1520 h_blank_end 1848 h_border: 0
(II) fglrx(0): v_active: 900 v_sync: 903 v_sync_end 909 v_blanking: 926 v_border: 0
(WW) fglrx(0): Unknown vendor-specific block f
(II) fglrx(0): LP141WP2-TLB1
(II) fglrx(0): EDID (in hex):
(II) fglrx(0): 00ffffffffffff0030ae364000000000
(II) fglrx(0): 00120103801e1378ea4b859257568a28
(II) fglrx(0): 20505400000001010101010101010101
(II) fglrx(0): 010101010101b027a08051841a303020
(II) fglrx(0): 360030be100000197021a09851841a30
(II) fglrx(0): 3020360030be100000190000000f0095
(II) fglrx(0): 0a32950a28191900320c3c01000000fe
(II) fglrx(0): 004c503134315750322d544c4231001f
(II) fglrx(0): End of Display1 EDID data --------------------
(II) fglrx(0): Output LCD using monitor section LCD
(II) fglrx(0): Output DFP1 has no monitor section
(II) fglrx(0): Output CRT1 has no monitor section
(II) fglrx(0): EDID vendor "LEN", prod id 16438
(II) fglrx(0): Printing DDC gathered Modelines:
(II) fglrx(0): Modeline "1440x900"x0.0 101.60 1440 1488 1520 1824 900 903 909 926 -hsync -vsync (55.7 kHz)
(II) fglrx(0): Modeline "1440x900"x0.0 85.60 1440 1488 1520 1848 900 903 909 926 -hsync -vsync (46.3 kHz)
(II) fglrx(0): Output LCD connected
(II) fglrx(0): Output DFP1 disconnected
(II) fglrx(0): Output CRT1 disconnected
(II) fglrx(0): Using user preference for initial modes
(II) fglrx(0): Output LCD using initial mode 1440x900
(++) fglrx(0): DPI set to (96, 96)
(==) fglrx(0): Using gamma correction (1.0, 1.0, 1.0)
(==) fglrx(0): QBS disabled
(==) fglrx(0): FAST_SWAP disabled
(==) fglrx(0): PseudoColor visuals disabled
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(==) fglrx(0): NoAccel = NO
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/lib/xorg/modules//libxaa.so
(II) Module xaa: vendor="X.Org Foundation"
compiled for 1.6.3, module version = 1.2.1
ABI class: X.Org Video Driver, version 5.0
(==) fglrx(0): NoDRI = NO
(==) fglrx(0): Capabilities: 0x00000000
(==) fglrx(0): CapabilitiesEx: 0x00000000
(==) fglrx(0): cpuFlags: 0x8000001d
(==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
(==) fglrx(0): UseFastTLS=0
(==) fglrx(0): BlockSignalsOnLock=1
(II) fglrx(0): Finished Initialize PPLIB!
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b](OprU)
[5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b](OprU)
[6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b](OprU)
[7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b](OprU)
[10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b](OprU)
(II) fglrx(0): driver needs X.org 1.4.x.y with x.y >= 99.906
(WW) fglrx(0): could not detect X server version (query_status=-1)
(II) Loading extension ATIFGLRXDRI
(II) fglrx(0): doing DRIScreenInit
(II) fglrx(0): DRIScreenInit for fglrx driver
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenByBusid: drmOpenMinor returns 11
drmOpenByBusid: drmGetBusid reports PCI:1:0:0
(II) fglrx(0): [drm] DRM interface version 1.0
(II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:1:0:0"
(II) fglrx(0): [drm] added 8192 byte SAREA at 0xcd000
(II) fglrx(0): [drm] mapped SAREA 0xcd000 to 0x7f3e01f4b000
(II) fglrx(0): [drm] framebuffer handle = 0xce000
(II) fglrx(0): [drm] added 1 reserved context for kernel
(II) fglrx(0): DRIScreenInit done
(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0): Name: fglrx
(II) fglrx(0): Version: 8.63.2
(II) fglrx(0): Date: Jul 2 2009
(II) fglrx(0): Desc: ATI FireGL DRM kernel module
(II) fglrx(0): Kernel Module version matches driver.
(II) fglrx(0): Kernel Module Build Time Information:
(II) fglrx(0): Build-Kernel UTS_RELEASE: 2.6.30-ARCH
(II) fglrx(0): Build-Kernel MODVERSIONS: no
(II) fglrx(0): Build-Kernel __SMP__: yes
(II) fglrx(0): Build-Kernel PAGE_SIZE: 0x1000
(II) fglrx(0): [drm] register handle = 0x000cf000
(II) fglrx(0): Display width adjusted to to 2816 due to alignment constraints
(II) fglrx(0): DRI initialization successfull!
(II) fglrx(0): FBADPhys: 0xc0000000 FBMappedSize: 0x0106a000
(II) fglrx(0): FBMM initialized for area (0,0)-(2816,1528)
(II) fglrx(0): FBMM auto alloc for area (0,0)-(2816,1024) (front color buffer - assumption)
(II) fglrx(0): Largest offscreen area available: 2816 x 504
(==) fglrx(0): Backing store disabled
(II) Loading extension FGLRXEXTENSION
(II) Loading extension ATITVOUT
(II) fglrx(0): DPMS enabled
(**) fglrx(0): Textured Video is enabled.
(II) LoadModule: "glesx"
(II) Loading /usr/lib/xorg/modules//glesx.so
(II) Module glesx: vendor="X.Org Foundation"
compiled for 1.4.99.906, module version = 1.0.0
(II) Loading extension GLESX
(II) fglrx(0): GLESX enableFlags = 94
(II) fglrx(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
Solid Horizontal and Vertical Lines
Driver provided ScreenToScreenBitBlt replacement
Driver provided FillSolidRects replacement
(II) fglrx(0): GLESX is enabled
(II) LoadModule: "amdxmm"
(II) Loading /usr/lib/xorg/modules//amdxmm.so
(II) Module amdxmm: vendor="X.Org Foundation"
compiled for 1.4.99.906, module version = 1.0.0
(II) Loading extension AMDXVOPL
(II) fglrx(0): UVD2 feature is available
(II) fglrx(0): Enable composite support successfully
(II) fglrx(0): X context handle = 0x1
(II) fglrx(0): [DRI] installation complete
(==) fglrx(0): Silken mouse enabled
(==) fglrx(0): Using HW cursor of display infrastructure!
(==) fglrx(0): Using software cursor
(II) fglrx(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(--) RandR disabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
(WW) AIGLX: 3D driver claims to not support visual 0x33
(WW) AIGLX: 3D driver claims to not support visual 0x34
(WW) AIGLX: 3D driver claims to not support visual 0x35
(WW) AIGLX: 3D driver claims to not support visual 0x36
(WW) AIGLX: 3D driver claims to not support visual 0x37
(WW) AIGLX: 3D driver claims to not support visual 0x38
(WW) AIGLX: 3D driver claims to not support visual 0x39
(WW) AIGLX: 3D driver claims to not support visual 0x3a
(WW) AIGLX: 3D driver claims to not support visual 0x3b
(WW) AIGLX: 3D driver claims to not support visual 0x3c
(WW) AIGLX: 3D driver claims to not support visual 0x3d
(WW) AIGLX: 3D driver claims to not support visual 0x3e
(WW) AIGLX: 3D driver claims to not support visual 0x3f
(WW) AIGLX: 3D driver claims to not support visual 0x40
(WW) AIGLX: 3D driver claims to not support visual 0x41
(WW) AIGLX: 3D driver claims to not support visual 0x42
(WW) AIGLX: 3D driver claims to not support visual 0x43
(WW) AIGLX: 3D driver claims to not support visual 0x44
(WW) AIGLX: 3D driver claims to not support visual 0x45
(WW) AIGLX: 3D driver claims to not support visual 0x46
(WW) AIGLX: 3D driver claims to not support visual 0x47
(WW) AIGLX: 3D driver claims to not support visual 0x48
(WW) AIGLX: 3D driver claims to not support visual 0x49
(WW) AIGLX: 3D driver claims to not support visual 0x4a
(WW) AIGLX: 3D driver claims to not support visual 0x4b
(WW) AIGLX: 3D driver claims to not support visual 0x4c
(WW) AIGLX: 3D driver claims to not support visual 0x4d
(WW) AIGLX: 3D driver claims to not support visual 0x4e
(WW) AIGLX: 3D driver claims to not support visual 0x4f
(WW) AIGLX: 3D driver claims to not support visual 0x50
(WW) AIGLX: 3D driver claims to not support visual 0x51
(WW) AIGLX: 3D driver claims to not support visual 0x52
(WW) AIGLX: 3D driver claims to not support visual 0x53
(WW) AIGLX: 3D driver claims to not support visual 0x54
(WW) AIGLX: 3D driver claims to not support visual 0x55
(WW) AIGLX: 3D driver claims to not support visual 0x56
(WW) AIGLX: 3D driver claims to not support visual 0x57
(WW) AIGLX: 3D driver claims to not support visual 0x58
(WW) AIGLX: 3D driver claims to not support visual 0x59
(WW) AIGLX: 3D driver claims to not support visual 0x5a
(WW) AIGLX: 3D driver claims to not support visual 0x5b
(WW) AIGLX: 3D driver claims to not support visual 0x5c
(WW) AIGLX: 3D driver claims to not support visual 0x5d
(WW) AIGLX: 3D driver claims to not support visual 0x5e
(WW) AIGLX: 3D driver claims to not support visual 0x5f
(WW) AIGLX: 3D driver claims to not support visual 0x60
(WW) AIGLX: 3D driver claims to not support visual 0x61
(WW) AIGLX: 3D driver claims to not support visual 0x62
(WW) AIGLX: 3D driver claims to not support visual 0x63
(WW) AIGLX: 3D driver claims to not support visual 0x64
(WW) AIGLX: 3D driver claims to not support visual 0x65
(WW) AIGLX: 3D driver claims to not support visual 0x66
(WW) AIGLX: 3D driver claims to not support visual 0x67
(WW) AIGLX: 3D driver claims to not support visual 0x68
(WW) AIGLX: 3D driver claims to not support visual 0x69
(WW) AIGLX: 3D driver claims to not support visual 0x6a
(WW) AIGLX: 3D driver claims to not support visual 0x6b
(WW) AIGLX: 3D driver claims to not support visual 0x6c
(WW) AIGLX: 3D driver claims to not support visual 0x6d
(WW) AIGLX: 3D driver claims to not support visual 0x6e
(WW) AIGLX: 3D driver claims to not support visual 0x6f
(WW) AIGLX: 3D driver claims to not support visual 0x70
(WW) AIGLX: 3D driver claims to not support visual 0x71
(WW) AIGLX: 3D driver claims to not support visual 0x72
(II) AIGLX: Loaded and initialized /usr/lib/dri/fglrx_dri.so
(II) GLX: Initialized DRI GL provider for screen 0
(II) fglrx(0): Enable the clock gating!
(II) fglrx(0): Setting screen physical size to 381 x 238
(II) config/hal: Adding input device ThinkPad Extra Buttons
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 1.6.2, module version = 2.2.3
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 4.0
(**) ThinkPad Extra Buttons: always reports core events
(**) ThinkPad Extra Buttons: Device: "/dev/input/event6"
(II) ThinkPad Extra Buttons: Found keys
(II) ThinkPad Extra Buttons: Configuring as keyboard
(II) XINPUT: Adding extended input device "ThinkPad Extra Buttons" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us,no"
(**) Option "xkb_options" "grp:alt_shift_toggle"
(II) config/hal: Adding input device Macintosh mouse button emulation
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
(**) Macintosh mouse button emulation: (accel) filter chain progression: 2.00
(**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
(**) Macintosh mouse button emulation: (accel) set acceleration profile 0
(II) config/hal: Adding input device TPPS/2 IBM TrackPoint
(**) TPPS/2 IBM TrackPoint: always reports core events
(**) TPPS/2 IBM TrackPoint: Device: "/dev/input/event8"
(II) TPPS/2 IBM TrackPoint: Found 3 mouse buttons
(II) TPPS/2 IBM TrackPoint: Found x and y relative axes
(II) TPPS/2 IBM TrackPoint: Configuring as mouse
(**) TPPS/2 IBM TrackPoint: YAxisMapping: buttons 4 and 5
(**) TPPS/2 IBM TrackPoint: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "TPPS/2 IBM TrackPoint" (type: MOUSE)
(**) TPPS/2 IBM TrackPoint: (accel) keeping acceleration scheme 1
(**) TPPS/2 IBM TrackPoint: (accel) filter chain progression: 2.00
(**) TPPS/2 IBM TrackPoint: (accel) filter stage 0: 20.00 ms
(**) TPPS/2 IBM TrackPoint: (accel) set acceleration profile 0
(II) config/hal: Adding input device Logitech USB Receiver
(**) Logitech USB Receiver: always reports core events
(**) Logitech USB Receiver: Device: "/dev/input/event9"
(II) Logitech USB Receiver: Found 20 mouse buttons
(II) Logitech USB Receiver: Found x and y relative axes
(II) Logitech USB Receiver: Found scroll wheel(s)
(II) Logitech USB Receiver: Configuring as mouse
(**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
(**) Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: MOUSE)
(**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
(**) Logitech USB Receiver: (accel) filter chain progression: 2.00
(**) Logitech USB Receiver: (accel) filter stage 0: 20.00 ms
(**) Logitech USB Receiver: (accel) set acceleration profile 0
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event1"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us,no"
(**) Option "xkb_options" "grp:alt_shift_toggle"
(II) config/hal: Adding input device Logitech USB Receiver
(**) Logitech USB Receiver: always reports core events
(**) Logitech USB Receiver: Device: "/dev/input/event10"
(II) Logitech USB Receiver: Found 1 mouse buttons
(II) Logitech USB Receiver: Found scroll wheel(s)
(II) Logitech USB Receiver: Found keys
(II) Logitech USB Receiver: Configuring as keyboard
(II) Logitech USB Receiver: Adding scrollwheel support
(**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
(**) Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us,no"
(**) Option "xkb_options" "grp:alt_shift_toggle"
(II) config/hal: Adding input device Video Bus
(**) Video Bus: always reports core events
(**) Video Bus: Device: "/dev/input/event5"
(II) Video Bus: Found keys
(II) Video Bus: Configuring as keyboard
(II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us,no"
(**) Option "xkb_options" "grp:alt_shift_toggle"
(II) fglrx(0): EDID vendor "LEN", prod id 16438
(II) fglrx(0): Printing DDC gathered Modelines:
(II) fglrx(0): Modeline "1440x900"x0.0 101.60 1440 1488 1520 1824 900 903 909 926 -hsync -vsync (55.7 kHz)
(II) fglrx(0): Modeline "1440x900"x0.0 85.60 1440 1488 1520 1848 900 903 909 926 -hsync -vsync (46.3 kHz)
(II) fglrx(0): EDID vendor "LEN", prod id 16438
(II) fglrx(0): Printing DDC gathered Modelines:
(II) fglrx(0): Modeline "1440x900"x0.0 101.60 1440 1488 1520 1824 900 903 909 926 -hsync -vsync (55.7 kHz)
(II) fglrx(0): Modeline "1440x900"x0.0 85.60 1440 1488 1520 1848 900 903 909 926 -hsync -vsync (46.3 kHz)
Last edited by orjanp (2009-08-12 08:43:13)

Wireless Keyboard not working with Tungsten T5

Similar Messages

Maybe you are looking for