New small WIRED keyboard not working with bootcamp

Greetings from Stuttgart, Germany
I just bought one of these new small WIRED keyboards for my macbook pro (early 2008/not unibody).
It's working fine with OSX but not with my bootcamp vista business x64: the fn-key is not recognized. After inspecting the device manager I found out that the keyboard is not recognized as an Apple keyboard like my old one (with numeric keys).
Afer updating bootcamp to version 2.1 I uninstalled the keyboard from the device manager, plugged it in again and it was still not recognized as an Apple Keyboard
Is there a way to manually force vista to use apple keyborad driver? Or is there an update for bootcamp on its way to solve the problem?
Best wishes,
Wolfgang Gross

UPDATE: a possible solution that is NOT working:
in device manager, for both USB Human interface devices associated to the a hardware id (05AC/021E) of the keyboard:
Update driver > browse my computer.. > let me pick.. > show compatible hardware.. > Apple Inc./Apple keyboard 2.1.0..
Doesn't change the keyboard (mis-)behaviour

Similar Messages

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

New Applications model DOES NOT work with StandAlone OSD media

If you are able to create StandAlone OSD media, the new Applications model DOES NOT work with it.
- The creation of the media will be successful
- The application installation itself will be successful
Yet after the application is installed, it shows the correct process it needs to complete based on the return code in AppEnforce log, but does not process that information back to the the TS Manager so it appears to attempt to download a policy which fails
causing the task sequence to error out..
Thanks,
Squirre1

It is very similar to this description:
http://madluka.wordpress.com/2012/05/15/error-0x8000405-when-installing-applications-to-a-workgroup-system-during-build-and-capture-task-sequence/
It is using the application model, since it is not attached to the domain it is on a workgroup. But it is on standalone media and not during a build and capture sequence, it is during an OSD. But alot of the same puzzle pieces fit. Basically pointing to
the new applications model not working during standalone OSD when the MP is not available. i would say that not enough information is getting encapsulated into the Application when exported onto the StandAlone media.

Why won't my imac recognize a wired keyboard to work with a wireless track pad?

why won't my imac recognize a wired keyboard to work with a wireless track pad?

Which model iMac are you using?

Why my numeric key pad on my wired keyboard wont work with snow leopard?

Why my numeric key pad on my wired apple keyboard wont work with snow leopard?
Thanks - Farshad

What do you know, I figured out.
Go to System Preference > Universal Acces> Mouse > check the "Press the option key five times to turn mouse keys on or off.
Thanks

Brand New iMac and wired keyboard not working

I just bought a new iMac.The wired keyboard seems to work, the mouse is plugged into the keyboard and that works, and I can, somewhat make changes to the volume and other small changes. The ESC key works (I can turn off VoiceOver)but... I can not even get the computer up and going. I can not put in my name or other registration information.
Any ideas if the keyboard has some kind of other settings that I need to turn off. There is no software or anything else in the Mac that I know of. It is brand new and just arrived today.
Anyone have any suggestions?

I'm so sorry. I know this a bummer. But better to take it back. When you take it in, if they boot it and get it to work, make sure and shut down the iMac, wait about ten seconds and press the power button. Make sure it boots to the Desktop and that your keyboard functions as it should. Just make absolutely sure it works before you bring it back home. In fact, since you could not get through the registration process, perhaps they will go through that with you since had problems with it. Something isn't communicating between the iMac and the keyboard. Could be the USB ports, software/hardware ... hopefully they'll repair it to your satisfaction or replace it.
Carolyn
Message was edited by: Carolyn Samit

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.

Keyboard not working with Windows 7 Bootcamp

I am using Window 7 with bootcamp. Its been working fine but for some reason the keyboard doesn't appear to to work as I can't even sign in. I've tried rebooting several times but no joy.

Did you install the Windows support software? Did you check in Windows sytem to see if the drivers are working? Check the Boot Camp help documnets http://www.apple.com/support/bootcamp/ and visit the Boot Camp forum https://discussions.apple.com/community/windows_software/boot_camp

Fingerprint reader on Lenovo KUF0452 keyboard not working with Lenovo X1

Hi, I have a Lenovo KUF0452 keyboard with built-in fingerprint reader. Up until two weeks ago I had a two year old X1 Carbon laptop which co-existed happily with the keyboard - I could unlock Windows with a swipe of the keyboard's fingerprint reader. I've now replaced the old X1 with a brand new X1 Carbon and can no longer unlock Windows using the keyboard's fingerprint reader - I just get this error on the Windows 8.1 lock screen: "A match for the fingerprint was not found in the fingerprint database." I have the latest Lenovo Fingerprint Manager Pro installed and have used it to enroll a couple of fingerprints for the X1's fingerprint scanner, but when I try to use it to enroll fingerprints for the keyboard's scanner the app's progress bar doesn't move off 0%, so I assume the app isn't accepting the keyboard's fingerprint scanner as a valid input. The X1 is docked, with the lid shut, so I have no easy access to the laptop's fingerprint scanner which is why I want to use the keyboard's fingerprint scanner to unlock Windows. How can I get the keyboard's fingerprint scanner to work with my X1? Kind regards,

hi Avikiru,
Welcome to Lenovo Community Forums!
Can you try,
Remove the AC and the Battery
Hold the Power Button down for at least 15 sec.
Reconnect just the AC and see if that'll work
If not You can contact a Lenovo Support Team or a Local Technician to have the Keyboard connection checked.
Regards
Solid Cruver
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Z and v keys on wired keyboard not working

Been very pleased with the reliability of my 24" iMac to date, with very few (if any) problems worth mentioning till the last few days when the z and v keys on the fullsize aluminium keyboard originally supplied with the iMac no longer work?
Can anyone shed any light on why these keys refuse to work. Is it a case of throw the keyboard away, or is it a software issue?
I've rebuilt the permissions using Disk Utility which did find quite a few errors, but it didn't fix the problem of the missing Z and V buttons on the keyboard.
It may just be simply that the keyboard is worn out, but I'm no journalist and don't drink Coke or eat McDonalds burgers over the keyboard so see no reason why these particular keys have reason to stop working.
And please note, I'm typing this from the smaller wireless keypad which explains why I can still type the Z and V keys!

Thanks for the advice, I dug out my old G3 Mac keyboard, plugged it in, and it worked, so it is the keyboard that is faulty rather than the Mac - can't believe it's only lasted 5 years
Guess that it means a trip over to my local Apple Store to buy another keyboard, and knowing my luck, a few other items whilst I'm in there

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?

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?

Keyboard not working with Mail

I have a new iMac aluminum, and everything was working ok for a week or so. Then the keyboard Update popped up, so I downloaded it. Seemed ok for a day (maybe just until I shut off the machine, though.)
Now, most programs are fine, but within Mail, the Reply and Reply All buttons do not work. If I start up a new message, I can type just fine up until the first space. After the first press of the spacebar, all I get are alert sounds for every key pressed.
Also, cannot send any message (Send button and shortcut not working.)
Help! And thanks!
Message was edited by: Zinco

This problem in Mail is usually caused by some Launch Services cache or preferences corruption that affects the built-in spell checker. The following article describes how to manually reset Launch Services — the notes at the bottom of the article also provide information about the side effects of deleting each of the files involved:
Resetting Launch Services
If you prefer using a cache cleaning utility instead of following the manual procedure described in the previous article, take a look at this other article for general troubleshooting and cache-cleaning procedures. Actually, you should also verify/repair the startup disk (not just permissions), as described there:
Resolving Disk, Permission, and Cache Corruption
The most appropriate utility for this particular problem probably is Tiger Cache Cleaner, but you may also want to consider other utilities, such as OnyX, or Cache Out X, which are free. Whatever utility you choose, be sure to read this first:
Side effects of System cache cleaning
As an example, this is how you should proceed with OnyX:
1. Quit all applications.
2. Launch OnyX and enter your administrator password.
3. Go to Maintenance > Reset and check LaunchServices database.
4. Un-check any other pre-checked options.
5. Click the Execute button.
6. Restart the computer.

Why is my wired keyboard not working?

Hi All,
Most of the time if I plug my wired keyboard (standard Apple w/numpad) before I start it up it works OK, however if it is unplugged whilst it is on, then plugged back in again it won't be recognised. Other non wired keyboards are fine. Even if I shut-down the MacBook Air ('13), plug the keybaord back in, then start up, it does not work. What's weird is that it normallys resets itself by the next working day (I only use the keyboard at work, take my Mac home).
Any help would be greatly appreciated, I miss having the two extra USB's!
Cheers,
Nathan

Good Morning SwimmingNathan,
If you are having issues with your wired keyboard, try a different USB port. Then try resetting the System Management Controller (SMC) and PRAM. Here's how:
Intel-based Macs: Resetting the System Management Controller (SMC)
http://support.apple.com/kb/ht3964
About NVRAM and PRAM
http://support.apple.com/kb/HT1379
If you tried all of these steps and your issue persists, contact Apple technical support or take your keyboard to the nearest Apple Store or Apple Authorized Service Provider (AASP) for diagnosis. If you plan to visit an Apple Retail Store, make a reservation at the Genius Bar using http://www.apple.com/retail/geniusbar/ (available in some countries only).
Cheers,
- Judy

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)

New small WIRED keyboard not working with bootcamp

Similar Messages

Maybe you are looking for