Ultra 60 keyboard not detected

Hello, I have an Ultra 60, 2X450MHz, 2GB RAM, 2X 50GB HDD, Creator 3D. I recently used the Solaris 10 CD-ROM to format>analyze>purge the hard disks, which went without errors. Now I connect a Sun Type 5c KB/Type 5 mouse, and one of the following occurs at boot seemingly at random:
1. OBP message above banner "cannot detect keyboard layout fe (or c2 or co" and "using USA keyboard layout" followed by banner with "Keyboard present" therein; however when keys are pressed, only repeating 3's or "Keyboard error" appears after OK prompt. Or...
2. No message above banner, but banner displays no keyboard present; same 3's repeating or error upon keypresses. Or...
3. No banner at all, but message "keyboard not detected, sending input/output to ttya".
I am using this keyboard right now on an Ultra 5. I have tried another Type 5c and a Type 6 on the Ultra 60 with the same results. My questions:
1. Is this an OBP fault? How to serial console to this machine without it having a hostname in order to update the PROM?
2. Is this a mainboard fault, like in the keyboard jack or something? Do I need a new mainboard?
This happened overnight. The only thing I can think of that I did was that I used a Belkin adapter (with PS/2 ports and VGA port) to purge the hard disks, then plugged in a Sun KB/mouse along with a display adapter as soon as I acquired them. I am lost! Any thoughts or solutions would be appreciated. Thanks!

See my thread here
PS2 keyboard/mouse causes random shutdowns or doesnt work
In short there is no known solution, it is an manufacturing fault, usually swapping to USB and enabling USB keyboard and mouse in the BIOS will help.

Similar Messages

Keyboard not detected while installing

Hi All,
I have a HP netserver lp1000r machine.
I want to install solaris 10 on it.
The keyboard works fine for installation of other linux distros like Ubuntu server etc.
It works fine while i am configuring the BIOS.
Some how the solaris installation program is not able to detect it.
the keyboard is a normal PS/2 keyboard and works fine on the same machine for other linux distros and BIOS too.
Can any one tell me how to solve this problem as I am really eager to get some solaris experience. I will be using this machine for DHCP, DNS caching, proxy and other purposes.
Regards

I have been scouring the internet on my limited dial-up connection trying to find someone who had a definitive solution to this problem which I too have been stuck with.
What finally resolved this keyboard problem during that critical stage in the win xp setup was by:
1. Going to System Preferences>Keyboard and Mouse and check-marking "USE ALL F1, F2 ETC. KEYS AS STANDARD FUNCTION KEYS (when this option is selected, press the Fn key to use the special features printed on each key)" Before starting up Boot Camp,
2. and Unplugging the Mighty Mouse from the keyboard while my mac was rebooting.
Switching out the apple keyboard for a standard USB keyboard did not work (perhaps in hindsight, i should have plugged it in first before boot camp rebooted and tried to install win xp;)
Attempting time after time again did not solve the issue;
Neither did doing all the software updates, firmware updates and such while borrowing an ethernet cable connection from my local library;
I did not need to find another Win XP with SP2 nor did I need to find a USB keyboard;
Not even updating my Mac OS X from 10.5.2 to 10.5.5 or installing the new firmwares for the Apple aluminium keyboard was necessary it seems.
Just a simple checkmark to make the apple keyboard's F-keys primary and unplugging the Mouse from the keyboard before the WinXP install kicked in, allowed me to press Enter to proceed with the installation.
I also turned off the special functions of the mighty mouse like the center click and roll ball, but I felt obligated to post the solution to this problem - Do as you would be done by.
Hope this helps others who encounter this same problem, please confirm if I am correct. Good luck.

X220: external USB keyboard not detected in BIOS

Hi!
I use an external USB keyboard attached to the port replicator of my X220. When Windows is booted the keyboard works without any problems. But I cannot use the keyboard pre-boot, e.g. to enter the HDD password after starting up, to configure the BIOS, etc.
I tried all USB ports both of the port replicator and the X220. The keyboard is still not detected by the BIOS (Version 1.20) and there are no BIOS options to enable "USB keyboard support".
Has anyone experienced similar problems? Are there any solutions to get the keyboard detected by the BIOS?
Thank you for your support!

@beastiesoft and earthartja,
If I am not mistaken, we are discussing this on the T series thread. Check here.
http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T420-Not-recognizing-keyboard-before-OS-loa...
@someotherguy,
Drop you an email on this.
//JameZ
Check out the Community Knowledge Base for hints and tips.
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"!
X240 | 8GB RAM | 512GB Samsung SSD

MSI 845 Ultra: USB20 not detected in WinXP

Hello,
Recently I bought a computer based on a MSI 845 Ultra board (USB2.0 + RAID) I'm using WinXP Prof. als desktop O.S. Everytinh seems to work fine but the USB2.0 controller is not detected. Is there in the bios some thing that I should enable ? Do I need somekind of extra driver so that it can be discovered. The USB1.1 controllers are working fine; no problems! :P
Who can help me ?
Extra Info
MSI 845 Ultra (USB2.0 + RAID; MS6398
BIOS version 3.6
Windows XP Prof + SP1

Hi,
USB 2.0 is supported through external NEC chip.
This infos I found on MSI web.
NEC USB 2.0 Driver
Support model K7T266 Pro2-RU (MS-6380 Ver2.0), 845 Ultra-ARU (MS-6398)
Description
Add General ID: VEN_1033&DEV_00E0
-- Driver version: 2.0.3300.20300.
For K7T266 Pro2, this driver must be used together with BIOS Ver3.3 or after.
Note: For WinXP, please use Microsoft Windows Update to download driver from Microsoft or aquire the latest service pack
WinXP SP1 Download Website :
http://www.microsoft.com/windowsxp/pro/downloads/servicepacks/sp1/sp1lang.asp
Date 2003-4-28

K8T Neo-V / Keyboard not detected

Here are my specs:
Motherboard: K8T Neo-V
CPU: AMD Athlon64 3100+
RAM: Kingston 512 MB PC3200
AGP: ATI Radeon 9700 Pro
HD: Maxtor SATA 80 GB Drive
PSU: Xion 400 watt (14A Max on +12V1, 15A Max on +12V2)
What I get upon booting:
PS2 Keyboard Not Found
CMOS Checksum Bad
Press F1 to load SETUP
Press F10 to load default values and continue
I don't know what the problem could be. Needless to say, there's nothing I'm able to do without a keyboard.
I have tried booting with everything in the case, as well as on a piece of cardboard (the way it is now). I still get the same error.
I have tried four keyboards. I used two OLD PS2 Keyboards (P1 era), 1 newer PS2 Keyboard (although unsure of age), and 1 USB Keyboard with a USB-to-PS/2 Convertor. No success. All four keyboards are functional in my two other PC's.
Any ideas? I have never tried an MSI board before; I'm thinking that may have been a huge mistake. I've never had these problems before. Is it RMA time?

The motherboard was purchased online by a friend (as I'm simply building it for him). I asked him about this and he said everything indicates that it's new... but you never know. This could have been returned by another user. It was purchased as a Mobo+CPU combo, but still came in a "sealed" box.
I've cleared the CMOS several times during my troubleshooting, but not while unplugging the AC cord. I just unplugged the AC cord, and changed the CMOS jumper. I let it sit for a minute, swapped back the jumper and plugged in the cord. Had the same problem. Now it also adds "Date/Time not set" to the list of errors mentioned above.
Any other ideas

Iconia W700: Bluetooth keyboard not detected in Windows 10 x64

I am in the process of updating all the computers in my house to Windows 10 and it has been fairly painless so far for most of the devices. However, I cannot get my Iconia W700 tablet to recognize the Bluetooth keyboard. It is the keyboard with integrated cover, and I've followed the procedure, as stated on Acer's website, of holding the power button on the keyboard for 5 seconds to put it into discovery mode, and then adding a device from the Bluetooth device menu. Obviously the menus have new locations, but are not hard to find. I updated the Bluetooth driver on the tablet but that did not remedy the issue. I looked around and couldn't find any mention of this problem here or elsewhere, probably since Windows 10 just launched a few days ago.

Ok, so I'm not sure if the driver was actually the issue, but the Acer documentation on putting the Bluetooth keyboard into pairing mode requires you to press and hold the power button until the two LEDs on the keyboard start to alternate like on a police car. If someone is reading this and this still doesn't allow you to pair the keyboard, then here are the steps to get the proper Bluetooth driver: Open the Device Manager (right-click windows icon in bottom left)Expand the "Bluetooth" category in the Device ManagerRight click the Bluetooth driver (should be the first in the list if there are multiple devices listed)Click UninstallRestart the tablet. The Bluetooth driver will be reinstalled on reboot.Open the Device Manager again after you log inRight click the Bluetooth driver and click "Update Driver Software..."Select the option for Windows to search for the driver software.An update should be downloaded and installed.Now repeat the pairing steps detailed above, and you should see an option to pair the keyboard appear in your Bluetooth settings.I've subscribed to this thread so if anyone has a problem, just reply and I will try to help you sort it out.

Microsoft keyboard not detected

I connected a Microsoft Internet PS/2 Keyboard to one of the Mini's USB ports using a PS/2 to USB adaptor. The computer thinks there is no keyboard connected. Any suggestions? Thanks!!!

I didn't have luck with PS/2 to USB adapters myself. The Microsoft USB keyboard I have worked right away with the mini but my Honeywells, original IBM gave me problems.
One thing you can do is test out your PS/2 to USB adapter with the keyboard by plugging it back into a PC and seeing if it works fine under windows to test the adapter plug for proper wiring connectivity.

TS3048 unable to connect to keyboard. System does not detect keyboard even after switching on and off. Mouse working fine. Earlier was working fine. Keyboard is not detectable by I mac . Tried a different keyboard same problem.

Changed batteries of keyboard -initially connected but now does not connect. Used a diffeerent keyboard -same result. Keyboard not seen in bluetooth devices.Switching on and off as well as re booting has not helped. Keyboard light continues to blink.

Hey Gautam5058,
Thanks for the question, and welcome to Apple Support Communities.
The following articles provide troubleshooting steps that may help to resolve your issue:
Apple Wireless Keyboard: Difficulty during pairing process
http://support.apple.com/kb/TS1569
Bluetooth Quick Assist
http://support.apple.com/kb/HT1153
You may also want to try resetting your computer's PRAM and NVRAM.
To resolve this issue:
1. Turn the Apple Wireless Keyboard off.
- For an aluminum Apple Wireless Keyboard, hold the keyboard's power button for more than 3 seconds.
- For a white Apple Wireless Keyboard, turn over the keyboard, and turn the power switch to the off position.
2. Click the "Continue" button as the Setup Assistant instructs.
3. Power the Apple Wireless Keyboard back on.
4. Enter the 8-digit passkey and press Return. Important: You MUST press Return after you enter the 8 digit code.
Thanks,
Matt M.

MacBook Pro 13" Early 2011 Backlight Keyboard Not Working?! Software Problem...

So my "MacBook Pro 13" Early 2011" backlight keyboard hasn't been working. I have tried LabTick today, doesn't fix anything. Even in high or low lighting situations (dispite the Adjust keyboard brightness in low light being off) doesn't like to go on. It doesn't give me a circle with a cross like it does with that box checked in day light. It shows on the screen the
16 dots fully light after hitting F6 fully, just it doesn't light up. I one time had to reset my Mac OS at the Apple Store, it fixed the problem, but when I restored with a time machine backup, it went back to this software problem. How can I fix this?! What is wrong with my OS? Mountain Lion? How can I fix this?!

If it does not detect the display automatically, try going to system preferences>displays, click detect displays.

Audigy(1) Platinum PCI Not Detected By Installation CD In New Desk

Hello, I just updated to a new computer and pulled my Audigy Platinum SB0090 (with the front dri've panel) out of my old system and installed it in my new systemell E52 (AMD dual core)Windows XP SP23GB memory?) I disabled the onboard sound in the BIOS.2) Installed the Audigy Sound PCI card and dri've panel.3) Upon boot, Windows XP installs the Firewire and Gameport automatically. I tell it "no" when it prompts my to install audio device drivers.4) I try to install the current Audigy Platinum drivers from here, SBAX_WBUP2_LB_2_09_006, but it tells me no Audigy is detected and won't install.5)?I try to install the drivers from my original installation CD (PN: 220ML0003067) and am also?told that my?Audigy is not detected.6) The new PC has two PCI slots, 3 and 4. is PCIe6, 2 is PCIe. I've tried both PCI slots to no avail. The BIOS shows an audio device in whatever slot it is in. Partial Solution:7)? I went ahead a told Windows XP to search for drivers and it'sdid find?them on the original installation CD and installed them. I now have basic operations, but no dri've panel access. However, both installers above still cannot detect the Audigy. In Device Manager I now show:- Sound, video and game controllers-- Audio Codecs-- Creative Audigy Audio Processor (WDM)-- Creative Gameport-- Legacy Audio Drivers-- Legacy Video Capture Devices-- Media Control Devices-- Video Codecs?All of the above devices are working properly. Apparently I will not be able to easily get these installers to work. Is there a way I can manually?install the drivers neccessary to get current and full functionality of my Audigy and front dri've panel?Thanks

This is my view. It's all OK. It looks?if the Plug And Play function doesn't work. IRQ 0?Timer di sistema?OK
IRQ ?PS/2 Keyboard?OK
IRQ 4?Porta di comunicazione (COM)?OK
IRQ 6?Controller disco floppy standard?OK
IRQ 8?Orologio di sistema CMOS a tempo reale?OK
IRQ 9?Sistema compatibile ACPI Microsoft?OK
IRQ 9?SCSI/RAID Host Controller?OK
IRQ 3?Coprocessore matematico?OK
IRQ 5?Intel(R) ICH8 Family SMBus Controller - 283E?OK
IRQ 6?Intel(R) P965/G965 PCI Express Root Port - 29A?OK
IRQ 6?ASUS X950 SeriesOK
IRQ 6?Intel(R) ICH8 Family USB Uni'versal Host Controller - 2834?OK
IRQ 6?Intel(R) ICH8 Family PCI Express Root Port - 283F?OK
IRQ 7?Intel(R) ICH8 Family USB Uni'versal Host Controller - 2835?OK
IRQ 7?Intel(R) ICH8 Family PCI Express Root Port 6 - 2849?OK
IRQ 7?Generic Marvell Yukon Chipset based Ethernet Controller?OK
IRQ 8?Intel(R) ICH8 Family USB2 Enhanced Host Controller - 283A?OK
IRQ 8?Intel(R) ICH8 Family USB Uni'versal Host Controller - 2832?OK
IRQ 9?Intel(R) ICH8 Family USB Uni'versal Host Controller - 283?OK
IRQ 9?Intel(R) 8280HR/HH/HO SATA RAID Controller?OK
IRQ 2?Controller host Texas Instruments IEEE 394 compatibile OHCI?OK
IRQ 22?Creative Audigy Audio Processor (WDM)?OK
IRQ 23?Intel(R) ICH8 Family USB Uni'versal Host Controller - 2830?OK
IRQ 23?Intel(R) ICH8 Family USB2 Enhanced Host Controller - 2836?OK
IRQ 23?Controller host OHCI compatibile IEEE 394?OK
IRQ 23?Hauppauge WinTV-HVR 67xxx Capture Device?OK

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)

5th generation ipod not detected by my windows xp. works fine on other pc. performed necessary steps to remove and reinstall itunes but having same issue. is there a driver i can download to pc then direct to that specific location when installing?

5th generation ipod not detected by my windows xp. works fine on other pc. performed necessary steps to remove and reinstall itunes but having same issue. is there a driver i can download to pc then direct to that specific location when installing?

I have a similar issue - my iPod nano connects and is visible in Device Manager yet invisible in My Computer and iTunes. I've tried everything I can possibly think of to try and solve this myself, all in vain.
Mine is a nano 4G. I've been using it for quite some time without the slightest problem. I have been using WINAMP instead of iTunes to manage my darling nano.
Then, one fine day I bought a new computer and the nano would not show up in My Computer, though the nano display shows "Do not disconnect". On my old computer it worked (and still works) absolutely fine with win XP as well as with win7 (the later I currently use on my new/problematic computer, which I bought last summer and that's how long I've had this problem).
Of course, after several first attempts I gave up and installed iTunes. I've tried using the Apple support article "iPod not recognized in 'My Computer' and in iTunes for Windows":
- reset
- fully charged,
- cable works fine on two other computers
- in normal or disk mode makes no difference
- tried to find anything useful in the diagnostics mode
- reinstalled iTunes several different times since then to the latest version
- I've unplugged every other USB device except for my mouse and keyboard and tried several different USB ports on my motherboard (USB 3.0 and conventional), as well as trying different USB- related options in my BIOS.
- I've never used any Mac with this ipod
- I've tried fiddling with the win7 Services by stopping and restarting them and of course
- uninstalling the iPod drivers in Device Manager. After such an uninstall the ipod would automatically be recognised and "ready for use", i.e. being invisible in My Computer.
- Attempted to find any possible third-party conflict with msconfig or the possibility that my ipod is being confused for a network drive (for which I've disconnected my HDD, leaving only my SSD with the OS).
Sometimes, iTunes would note that iPod service (or something, can't remember exactly) failed to install properly and asked to try and repair it. I would click YES! and voila - no change! The ipod would rarely show up in iTunes on my problematic computer like this:
iTunes would warn me that the nano would need restoring so I would try and do it on my haunted machine upon which iTunes would freeze like you seen in the picture.
Despite this, I've updated and restored the nano on my father's computer to the latest version without any problems. This though, did not solve my problem in any way.
I can load music to my nano through my old computer (which for me is a real pain and hassle) and the gadget works normally in terms of its disconnected functionality.
I've taken my nano to the local service for repair and they said it was fine. Mercifully, they didn't charge for the diagnostics service (gee, thanks for not ripping me off!).
Here are two screengrabs from my Device Manager
and Devices and Printers screens on my comp:
That is my sad story as far as I can remember. It's most likely something with the drivers or something along those lines though I'm out of ideas at this point.
If you think you have any idea PLEASR HELP, I'M DESPERATE!

HP Color LaserJet CP1217 is not detected by PC

Hi
I have a HP Color LaserJet CP1217 which I am trying to connect by USB to a new computer running Windows 8.
When I first plugged the printer in the drivers were automatically detected and downloaded, and the printer was working.
I then moved the printer to a different PC for another printing job. Also worked fine.
When I brought the printer back to the new computer, the printing jobs were just getting stuck in the queue with an undescriptive error message.
I tried various combinations of restarting the PC, uninstalling drivers, re-installing drivers, updating drivers, turning printer on and off, using the HP print and scan doctor.
Using the HP print and scan doctor I am getting a message that the printer is not connected - though the USB cable is plugged in. I have tried different USB ports and a different USB wire but still the pc will not detect the printer.
These same cables work fine when I try the printer with another computer so it is obviously some other issue.
As the printer is more than five years old HP will not help over the phone. They recommend we buy a new one. But this one was working a few days ago!
Help please.

Hi
Yes other USB devices work (USB drive,keyboard etc).
Initially there was an error in the printing dialogue box but just said "error" with no other details.
Since un-installing drivers and re-installing, no printer is detected, only the printer driver. The printer is on and plugged in. When I go to devices and printers and run 'add printer' command it does a search and comes up with nothing.
Running windows 8.1, 64 bit.

Seagate Hard Drives not detected by the Windows 7 installer

I've spent hours on this trying every conceivable reason, so I apologize in advance for the length on this post.
I connected a Seagate 320GB 7200.10 hard drive to a P35 chipset system and attempted to install Windows 7 RTM onto it. The installer got to the part of detecting hard drives, but could not detect this drive. Native SATA mode was enabled, and AHCI was enabled.
I disabled Native SATA mode, then after that failed I also tried disabling AHCI by setting the controller to IDE mode. Still, the Windows 7 installer refused to detect the drive.
I replaced both the SATA & power cables, verified the drives are detected by the AHCI firmware and the BIOS, and I even tried different motherboard SATA ports to no effect. I took a second , identical Seagate 320GB SATA hard drive, this time pre-formatted it inside Windows 7 RC using NTFS defaults, and again (with and without AHCI and Native SATA mode) Windows 7 will not see this hard drive either!
I even downloaded the AHCI preinstall drivers and loaded these using a flash drive. When I did Windows 7 would autodetect the ICH9 driver and I would click Next. Windows 7 would suddenly see the drive, but all options to format or create a partition are grayed out. Clicking the more info button gives me this error message:
"Windows cannot be installed to this disk. This computer hardware may not support booting to this disk. Ensure that the disk's controller is enabled in the computer's BIOS menu."
I used the AHCI preinstall drivers specific for the motherboard (Vista 64) and I also tried the AHCI preinstall drivers from Intel for Windows 7 RC 64. As of this writing Intel has not released official Windows 7 RTM Intel Matrix Storage Manager drivers.
In frustration I installed a SSD (with AHCI and Native SATA mode enabled) and suddenly Windows 7 detects the SSD without needing to load any driver (as would be expected, since Vista and 7 include Intel Storage Manager drivers by default already). I installed Windows 7 RTM 64bit onto the SSD without issue.
15 minutes later I was at the Windows 7 desktop, and Windows 7 was showing the Seagate 320GB hard drive under "My Computer" as normal. I could even use the Seagate hard drive as normal as if nothing was wrong. For kicks I launched the Windows 7 installer inside Windows 7, but as you can see below it still refused to see the drive, despite the drive being shown under My Computer:
(Since I can't use thumbnails, here's the direct link: http://i111.photobucket.com/albums/n129/Chanur64/Box/Howpossible.jpg )
Also I should note I previously had Windows 7 Beta installed on an IDE drive in this exact system, and had no problems with it. Windows 7 RTM would allow me to install to an IDE drive and allowed me to install to an SSD, but it cannot see and cannot install onto both Seagate 320GB hard drives. These Seagates are known good drives previously part of a RAID 5 array.
If anyone knows what is going on or has some ideas I've not tried I would love to hear from you and get this figured out. Suffice to say this is not a promising start for Windows 7.
Intel Q6600
Gigabyte GA-EP35-DS4 (ICH9R southbridge)
4GB DDR2-800
2x Seagate 320GB SATA 7200.10
Intel X25-M 80GB
8800GTS 320mb
PC Power & Cooling 750w PSU

I just had to solve the same issue with a Seagate Momentus Thin hard drive (
http://www.seagate.com/www/en-us/products/laptops/slim-laptop-hard-drives/)
Tried several BIOS configuration, AHCI drivers, etc and Windows 7 32bits couldn't detect the drive.
My solution was to boot with a USB pendrive with HirenCD tools (http://www.hiren.info/) and use a partition manager to erase disk contents, create and format a partition.
Windows 7 detected the hard drive for the first time and now is installing, so.. crossing fingers.
Thanks,
Diego
Diego,
Thanks for the information and the link to Hiren.info! I'm creating my bootable flash drive now. I'll report back if I get this to work.
I had this same issue on a Seagate Momentus 7200.2 "laptop" hard drive. I say "lap top" in quotes because it's actually in a desktop (HP Compaq Ultra-slim dc7800). I believe it was an upgrade, so it took me a while to figure out what I was dealing
with until I finally took out the harddrive and checked what company made it!
Thanks everyone!

Surface Pro 3 / "Windows did not detect a properly installed network adapter"

Hi all,
I've been running the Windows 10 Technical Preview (9926) on my Surface Pro 3 successfully
since January. Unfortunately, I lost all internet connectivity today.
The problem started when I noticed the type cover wasn't working (pressing keys on the type
cover wasn't registering any typing on my screen) and my USB mouse wasn't working either. I tried removing and reattaching the type keyboard but this didn't fix the issue. I had to use the accessibility on-screen keyboard to sign into Windows (thankfully touch
was still working). Once I signed in, I still didn't have typing or cursor ability, so I decided to restart the computer.
Then it got worse. I noticed the Surface Pro 3 was stuck on "restarting" and wouldn't
actually restart. Since it wasn't responding, I held down the power button for about 10 seconds until it turned off. When I turned it back on, the type cover and mouse started working again.
Unfortunately, this is when the WIFI problems began. I had WIFI for a few seconds, and then
I lost internet. I disconnected/reconnected but there was a yellow triangle telling me there was some sort of problem. So I restarted the Surface Pro 3.
When it came back on, there were suddenly NO connections available at all. Opening the "Network
& Internet" settings page gave me the message "Windows did not detect a properly installed network adapter". And here I am, without internet on my Surface Pro 3, borrowing my friend's computer so I can type this message (he is also running
Windows 10 build 9926 on his laptop and is able to connect to my WIFI with no problems, whereas my Surface Pro 3 cannot even detect any networks). I have not dropped or damaged the SP3 in any way, and there have been no storms or power outages or anything
of that sort. Any ideas what could have happened to the WIFI on my Surface Pro 3?
Thanks for your help...
Ethan

Hi Ethan,
Currently, there are a few compatibility issue between the current hardware and Windows 10 Technical Preview (9926 build), this is mostly related to driver compatibility issue.
I suggest you download the latest network adapter driver package to install, when it is finished, check if it appears under Device Manager.
Surface Pro 3, Surface Pro 2, and Surface Pro firmware and driver packs
https://www.microsoft.com/surface/en-us/support/networking-and-connectivity/install-wireless-drivers
You can check if you can install the latest firmware package for your device.
Here is an article to talk about such things:
Windows 10 January Technical Preview on Surface
https://www.microsoft.com/surface/en-us/support/install-update-activate/windows-technical-preview#Known
Regards,
Alex Zhao
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Ultra 60 keyboard not detected

Similar Messages

Maybe you are looking for