Thinkpad W530 Mini DisplayPort broken
I bought my Thinkpad W530 about 8 months ago, and I have been experiencing issues with the mini dp port. When I look at the port, it seems that it "went inside" the laptop a littlebit, so I couldn't conect it to monitors.
I am just asking if it is covered in the warrenty, and if yes, how can I go and fix it?
Any help would be greatly appreciated.
Solved!
Go to Solution.
Hi Jimgao,
Welcome to Lenovo Community!
As per the query we understood that you are facing issue with DP on your ThinkPad W530.
This is a physical damage and it won’t cover under normal warranty, if the system is having ADP (Accidental Damage Protection) then it will cover, but the warranty policy will differs from region to region. You can check the warranty status and what type of warranty your system is having from the below link, and call the customer care if any help needed.
http://shop.lenovo.com/SEUILibrary/controller/e/webca/LenovoPortal/en_CA/config.workflowtartWarranty
Hope this helps.
Best regards,
Hemanth Kumar
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!
Similar Messages
-
Using the mini displayport to HDMI on W530
I have read thru the similar threads regarding using the mini displayport on the W530 and seem to get some conflicting info.
I bought an mini display port to HDMI adapter and am trying to connect it to my Samsung monitor and it does not work, no signal is detected in either extend or duplicate mode.
What BIOS settings do I need to set (mine are currently at the default) and what drivers if any do I need to update to make this work?
When using the vga adapter port with the same monitor it works with no additional changes.
Solved!
Go to Solution.One more thing...
It is recommended to use a single straight-through cable with the proper connector at each end (i.e. miniDP->HDMI), rather than use a 2-part arrangement with a short miniDP->HDMI adapter, along with a normal HDMI-to-HDMI cable. Sometimes the adapter used is the source of the problem, and the externally HDMI-connected monitor is just not seen correctly at the right time for the HDMI handshake that is required. Hence the symptom.
I'd at least try a plain straight miniDP->HDMI cable, instead of using an adapter+cable. It's only a few dollars. -
Problems projecting W530 via mini-displayPort to HDMI TV
I am having problems attempting to project to a TV connected via HDMI to my W530 using a mini-DisplayPort to HDMI conversion cable. The TV goes into an initializing connection mode then states unsupported format. I have tried discrete and Optimus video modes in the BIOS, but for the life of me I cannot project to my HDMI TV. Any ideas?
What cable or adapter are you using? I have no need for that particular conversion so I have not tried, but if I were going to, I would probably use http://www.monoprice.com/products/product.asp?c_id=104&cp_id=10428&cs_id=1042802&p_id=5311&seq=1&for... for starters.
Usually monoprice products work well enough and their prices rock. -
ThinkPad W530 Mobile Broadband Mini Card
Hi all.
I've recently buyed a ThinkPad W530 (Lenovo Model Number: N1K4JIX).
Tecnical sheet and distributor sheet say that in this model there is an "3G Open SIM" WWAN card. In fact, i've under the battery the slot for insert my 3G Telephon VODAFONE SIM.
The problem is that i not can see nothing (software or hardware switch) that can control 3G Broadband connection.
I update the notebook at Win8, with shipped Lenovo CD, i try to install ERICHSON drivers but this give me error (it's impossible initialize device).
Now, my intret is in first how i know if i really have an Mobile Broadband Mini Card installed and not only the SIM slot and, after iìm sure of this, how can i enable and use 3G connection with my laptop?
Thank very much at all,
regards,
Mauro.Don't hold me to it but the Wan Miniport 2 I don't actually think is the Ericsson card
If the drivers aren't installed it would display under other devices if it was included in your system
A lot of W530 systems to my knowledge don't come with the WWAN installed, it is WWAN Upgradeable and has a Sim slot and the antennae cables already there, mine was like this and I had to remove the keyboard and install the WWAN card (cost : £100ish)
DangerMouse
Current Machines : T420s/W530/X1CT -
Just wanted to give a heads up about a review of the W530 that's written by a user who owns the W520, so it's heavy on comparisons which is kind of helpful if you're familiar with that machine. I'll quote the whole review below sans all the images to prevent bandwidth warnings! Also truncated and removed some sections to get under the 20,000 character count limit Full review with images is here: http://www.laptopreviews.com/lenovo-thinkpad-w530-review-2012-07
Just like last calendar year, Lenovo is ahead of Dell and HP in releasing a workstation equipped with the latest and greatest Intel Core processors and nVidia Kepler professional graphics. Starting at $1,299 on Lenovo.com (which is the same starting price as the W520 when it was introduced), the Lenovo Thinkpad W530 can be configured with processors ranging from the Intel Core i5-3320M to i7-3610QM to the top-end i7-3290XM, supports up to 32GB RAM and 270 nit 95% color gamut FHD display for demanding business customers. The W530 is like the W520 in many ways as a professional workstation laptop.
The Thinkpad W530 under review comes with the following specs:
Processor: Intel Core i7-3520M (2.9GHz, TurboBoost to 3.6GHz, 4MB L3 cache)
Graphics: nVidia Quadro K1000M
Memory: 8GB RAM DDR3-1600MHz
Display: 15.6” 1600 x 900 resolution, matte finish
OS: Windows 7 Professional
Storage: 500GB 7200RPM
Battery: 6-cell Li-Ion, 57Whr
Wireless: Intel Centrino Advanced-N 6205
Ports: Gigabit Ethernet, VGA, mini-DisplayPort, powered USB 2.0, USB 2.0, USB 3.0 (x2), combination headphone/microphone jack, ExpressCard slot (34mm), SDHC reader, 1394
Weight: 5.95lbs (2.7kg)
Keyboard
Let’s just start off with the most obvious change. The new keyboard is the most radical change in the ThinkPad line since…forever, really. Up until now, the ThinkPad series has had the same keyboard style since introduction, with minor changes here and there. Replacing the traditional 7-row ThinkPad keyboard is the island-style 6-row keyboard, found on the whole range of ThinkPad's, from the 12” X230 all the way up to this 15.6” workstation. Even with the changes, the surface of each key has stayed the same during the transition (1.5cm by 1.5cm for the alphanumeric keys) as well as the spacing between each key (roughly 0.4cm). Other keys, such as Caps Lock, Enter, Shift, Backspace, etc., have stayed the same size as well, though the Caps Lock key no longer has an indicator light. Notable differences include shape changes in the Esc key, Delete key, moving the power button from top-center to top-right, and the lack of a dedicated Menu key. However, the most important changes in key layout are as follows:
The layout of the “special keys” (Delete, Home, End, PgUp and PgDn) has been dramatically rearranged on the new keyboard
The dedicated Forward/Back buttons are now gone. These buttons used to be located to the right/left of the Up Arrow key and are now replaced with the PgUp/PgDn keys
The Print Screen button is now located where the Menu button should be.
The Scroll Lock and Pause buttons have disappeared, though they have been relegated to near-oblivion in today’s world
And just for change’s sake (as far as I know), Lenovo decided to paint the Enter key black instead of the traditional ThinkPad blue and the Windows key is bigger on the W530 than the W520 (1.5cm squared vs. 1cm squared).
To those coming from an older ThinkPad, the newer keyboards are either something to love or something to hate. The older keyboard in previous generations were renowned for their quality and keyboard feel (certainly, they were one of the best laptop keyboard on the market) and is so popular that it has an almost religious following among ThinkPad users. On the flip side, the newer keyboard has a lot to prove to the ThinkPad community. While the common-used alphanumeric keys have the same area and spacing as the old keyboard and the typing quality on it is above average (compared to other island-style keyboards), Lenovo’s choice to move and kill off some special function keys fly in the face of what most ThinkPad users would want. I love using the Forward/Back buttons while browsing the internet and using Windows Explorer, for example, but with the current and likely future ThinkPad's killing those buttons off, I will miss being able to navigate with just my right pinkie. The choice to move the Print Screen button to the bottom of the keyboard just baffles me, period. It would have been nice if Lenovo had kept the 7-row layout while designing the new keyboard and if the keys had stayed in pretty much the same positions during the change (for example, “special keys” staying in the top-right, bringing back the Forward/Back buttons), I wouldn’t make too much fuss over the new style even though I personally prefer traditional keyboards. At least the Fn button stays in the bottom-left corner, an odd quirk that’s been featured on ThinkPad's for as long as I can remember.
Build and Design
Just like the W520 before it, the newer W530 is a tough machine, built well and meant to last. The outside casing of the laptop is made using ABS plastic, while the inside contains an internal rollcage to protect internal electronics in case of a drop or other accident. It also makes the laptop all but impossible to flex (there’s maybe a millimeter or two of flex when twisting the display). There is a keyboard draining system that will protect the laptop in the event of a small liquid spill onto the keyboard as well. Sturdy, metal hinges attach the display to the body of the W530, and they are firm enough to hold any angle they are set up despite any typical vibrations or other movements, and if the W520 is any indicator, they will stay firm for years to come.
As I’ve mentioned in my Thinkpad W520 review, Lenovo’s business laptops are certainly capable of withstanding a few drops onto the floor. Even with repeated drops, having the power brick fall onto the palm rest from several feet above, and traveling with the notebook unprotected in a backpack for just over a year, I’m sure that the W530 will be able to survive prolonged abuse for years to come.
One thing to note about the W530 (and workstation laptops in general) is the power brick. The version with the K1000M GPU comes with the 135W power adaptor and it’s just slightly smaller and lighter than an actual brick of the clay variety, coming in at 6in by 2.5in by 1.4in and 1.83lbs. Those considering buying a W530 with the K2000M will receive the 170W power adaptor (like my W520), which measures 6.5in by 3in by 1.4in and actually weighs less (1.7lbs) oddly enough.
Display
While the review unit came with a 900p, 220 nit HD+ display, the W530 is also available with a 768p 220 nit display (which I recommend against; 768p needs to stay in netbooks and bargain-bin laptops, not workstations) and a 1080p, 95% color gamut, 270 nit FHD display. Depending on the configuration options, either the 768p is the default and the 900p is a $50 upgrade, or the 900p is the default; the 1080p display is a $250 option, though after owning a W520 with said display, I highly recommend it if it’s in the budget. Both the W520 and W530 use the same model displays.
With the 1080p display to the left and 900p display to the right, the 50 nit difference shows. Compared to the HD+ display, the FHD appears to be noticeably brighter (though in photos, it shows as being more white-washed, though this is due to the camera and not the displays). Colors on the 95% gamut FHD are also more saturated than the HD+ display, though the HD+ display still has colors that pop out well. Black reproduction on either display is good, with both being very dark. Being TN panels, viewing angles on either is just average, though better than on glossy display found in most consumer laptops. Tilt either screen back far enough (they go just past 180 degrees) and colors turn into shades of black or extremely darker versions.
Sound
This is where the W530 makes the W520 look shameful. Owners of the W520 workstation laptop would either have to use an external speaker set, headphones, or have to perform modifications in order to have a laptop that sounds half-way decent. The W520 speakers were low volume (even when at 100%), had no depth, and would sound tinny when playing near 100% and/or playing high-pitch noises.
In contrast, the W530 actually sounds amazing. In my review of the Thinkpad W520, I contrasted the W520 to a Dell XPS 15 with JBL speakers, concluding that the only way to get good sound from a W520 was to use a different sound solution from the internal speakers. However, I feel that the W530 can compete with media center laptops in terms of audio performance, a major plus over the previous generation Lenovo workstation. This is in thanks to different audio drivers (the W520 uses the Conexant 20672 SmartAudio HD drivers, and the W530 uses Realtek High Definition Audio) and Lenovo’s inclusion of Dolby Home Theater v4 software, which I went into detail about in the Ideapad U310 review. In a nutshell, this software includes a few factory-shipped sound profiles and settings appropriate for different usage scenarios, which allow a user to enhance voice quality (in the Movie profile) or to enjoy rich sound when listening to music (in the Music profile and various settings). While the W520 was tinny and lacked bass, the W530 can reproduce sounds from any pitch found in music and gives great bass for a laptop lacking a subwoofer.
Software
Unlike the previous W520, Lenovo’s ThinkPad W530 comes with a bit of bloatware out of the box. Of course, there is the typical trial AV software, Intel WiDi, and Microsoft Office Starter 2010, though this is to be expected in pretty much any laptop bought today. Also included is a trial of Nitro Pro 7, a PDF editing suite, and Corel DVD MovieFactory (Lenovo Edition). Lenovo also includes a cloud storage solution called “Lenovo Cloud Storage by SugarSync”. Skype is also included on the W530 and with the integrated camera, the video coming from the W530 user looks clear and colorful.
Lenovo also includes some excellent software as well. My personal favorite is the Lenovo Power Manager 6, which is like the default Windows power manager on steroids. A user can change system settings (CPU deep sleep, display brightness, ODD power, etc.), idle timers (when to stop the HDD, dimmed display brightness, standby and hibernation), advanced settings (allow/disallow hybrid sleep and wake timers, power management for PCIe, USB, CPU, and system cooling), events and alarms. By default, it comes with six power profiles (Power Source Optimized, Max. Performance, Max. Battery Life, Video Playback, Energy Saver (which actually drains more power than Max. Battery Life, oddly), and Timers off (for when a user wants to use the W530 in a presentation).
The best I can describe Lenovo SimpleTap as being is a Metro-like interface on top of Windows 7; either launching it from the Start menu or the blue ThinkVantage button on the keyboard will activate it, resulting in the traditional Windows desktop being replaced with a Metro-style tile system and a toolbar on the top-right corner. The user can always exit out of this interface by either pressing the Escape key or clicking on the SimpleTap background. The included Thinkpad-branded fingerprint software is also excellent, allowing for a simpler and more secure way to log into Windows; I use it exclusively on my personal W520, though there is a setting to allow a user to log in with a password en lieu of a fingerprint. Last but not least is the ThinkVantage Tools suite, which includes the above ThinkPad applications, plus: Password Vault, Update and Drivers, Airbag Protection (an active protection system for the HDD), Factory Recovery Disks, Messages from Lenovo, Enhanced Backup and Restore, Internet Connections System Health and Diagnostics, and Web Conferencing.
In the case of a fresh Windows install, a user can always download the Thinkpad-branded software from Lenovo’s website. If anything, I recommend keeping the Power Manager software.
Battery Life
Not using Power Manager’s Battery Stretch, the Lenovo Thinkpad W530 was able to last six hours and 46 minutes while having the display brightness set to 5 out of 15 and only using the Intel GPU (Optimus disabled). The 6-cell battery was also able to last five hours and 25 minutes under those same conditions, but also included a 45 minute YouTube video. Using the same settings, but running solely on the K1000M, the W520 manages a battery life of three hours and 52 minutes.
Out of curiosity, I tried installing my W520’s 9-cell battery into the W530, and while it fitted correctly, there were some issues. If a user tries booting with the older battery, the W530 will stop booting and display the following message:
The battery installed is not supported by this system and will not charge. Please replace the battery with the correct Lenovo battery for this system. Press the ESC key to continue.
What that means is that even if the W530 is plugged into its charger, the laptop will still not recharge the battery. This is because the older batteries lack an authentication chip inside of them (found in OEM batteries in the -30 series of Thinkpads). A user can still use an older battery with the system, but will have to find some other means to charge up other than the W530.
User Upgradability
If you know how to use a screwdriver, you can upgrade the W530 yourself with aftermarket parts. Lenovo, in a way, even encourages this by publishing their service manuals online. To access RAM slots 3 and 4 and to access the hard drive bay, all that’s needed is to remove the only two doors on the underside of the laptop, three screws total. This ThinkPad ships with a Hitachi Z7K500 500GB 7200RPM hard drive and no RAM in the last two slots (out of a total of four slots, allowing 32GB of RAM maximum).
To gain access to the rest of the components, there are two additional screws located on the bottom that must be undone. One is located right next to the RAM module door (towards the front edge of the laptop) and the other is located within the RAM module area itself. When these are gone, all one needs to do to remove the keyboard is to slide it towards the display, lift from the bottom edge near the trackpad, and carefully move towards the trackpad. First thing I noticed was that the size, shape, and connector is the same for both the W530’s keyboard and W520’s keyboard, so it might be possible to put an traditional ThinkPad keyboard into this Ivy Bridge system. However, there are additional keys on the W520’s keyboard that are not found on the W530 (Screen Lock, Forward/Back keys, etc.) and the BIOS probably would not know how to handle those extra keys. Anyway, Lenovo ships out this particular system with two sticks of generic Samsung memory (4GB each), an Intel 6205 WiFi card, and a slot for either a WWAN card or mSATA SSD (only one can be installed at a time). If an end user must have both, they could install the mSATA SSD and use an ExpressCard 3G cellular data card externally.
Conclusion
Like its predecessor, the W530 is a functional workstation laptop that’s first out of the gate with an array of Ivy Bridge processors to choose from. It can pack up to an Extreme Edition i7-3920XM, nVidia Quadro K2000 GPU, 32GB of RAM, 1080p display, and up to three system drives -- mSATA SSD, primary HDD bay, and another drive if you replace the optical bay with an Ultrabay HDD caddy. While not equipped with the more expensive options, our review unit is certainly a great workstation that will serve a professional well in any CUDA-based work (CAD, video or photo editing, graphics design, etc.). The most noticeable change between the W520 and W530 is the keyboard, and for a lot of potential buyers it will be a love it or hate it situation. For those buying into the ThinkPad line for the first time, it may not bother you too much. Those who are long-time ThinkPad users (such as myself) will probably be disappointed in the direction Lenovo has gone with the new design, but ignoring the odd arrangement of non-alphanumeric keys the new ThinkPad keyboard is actually a joy to type on. The curved keys fit well around the fingers, just like the old keyboard, and since the spacing between keys are the same it shouldn’t feel too different for those upgrading to a newer ThinkPad.
If history is any indicator, the ThinkPad W530 should not only be the first Ivy Bridge mobile workstation, but will also be the lightest of the bunch as well (the W520 was 5.95lbs, Dell’s Precision M4600 was around 6lbs, and HP’s Elitebook 8650w started at 6.5lbs). My only objective complaint about the W530 (ignoring the keyboard) is that Lenovo did not introduce an option for users to purchase one with a FirePro professional GPU (Quadro’s competition), found in workstations offered by Dell and HP. For those that do not need CUDA, it would have been a great, cost-effective solution while still staying with the legendary ThinkPad line.
Pros
Business-quality durability
Multiple storage drive options
Over 6.5 hours of battery life
IBM warranty support
Vastly improved sound quality (compared to the W520)
Cons
No Forward/Back keys, other missing keys
Cannot use previous-generation Lenovo OEM batteriesI think no one "normally" working will use touch specific elements of Win8! Metro is one part of Win8, but i think normal desktop mode will be preferred by 99 % of the users.
With the new upcoming Microsoft Surface, touch might work well, but i just don't see myself touching my laptop's screen.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------W520 4276CTO i7-2860QM Quadro2000M 1920x1080 16GB RAM - 160 GB Intel 320 SSD -
External monitor not detected on Thinkpad W530 intel-virtual-output
I'm having problems with connecting my ThinkPad W530 to external monitors since a few months. I'm using NVIDIA Optimus and bumblebee/optirun since the VGA and Mini DisplayPort connectors are only wired to the NVIDIA card om this laptop. For a long time I have executed:
$ optirun true
$ intel-virtual-output
Then I have started the Screens GUI tool in Gnome to setup the placement of the external screen but now the external screen is not present in the GUI tool and xrandr gives me:
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
LVDS1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm
1920x1080 60.00*+ 50.00
1400x1050 59.98
1280x1024 60.02
1280x960 60.00
1024x768 60.00
800x600 60.32 56.25
640x480 59.94
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
If I select "Discrete mode" and select startup screen as VGA in the BIOS the BIOS and the Grub screens shows on the external monitor but the screen locks on the screen that shows that the system is booting with the linux-ck kernel. This has never worked for me in Arch Linux so that is no surprise. In Ubuntu everything everything worked fine the last time I tried.
How can I debug this? Why is the external screen not detected any more?Thanks, I am not sure exactly how to read the logs but I cannot find anything that is obviously wrong
Below is my log with an external screen connected via Mini DisplayPort and after running:
$ optirun true
$ intel-virtual-output
a few times, no more logs seem to be added when I connect/disconnect the monitor or when I run the above two commands more times.
╰─➤ cat /var/log/Xorg.0.log 1 ↵
[ 2.616]
X.Org X Server 1.15.0
Release Date: 2013-12-27
[ 2.616] X Protocol Version 11, Revision 0
[ 2.616] Build Operating System: Linux 3.12.5-1-ARCH x86_64
[ 2.616] Current Operating System: Linux ethuil 3.13.9-1-ck #1 SMP PREEMPT Fri Apr 4 15:50:10 EDT 2014 x86_64
[ 2.616] Kernel command line: BOOT_IMAGE=/vmlinuz-linux-ck root=UUID=25086a9b-a542-4018-9f71-4f492f09be91 rw quiet rcutree.rcu_idle_gp_delay=1
[ 2.616] Build Date: 09 January 2014 08:47:24AM
[ 2.616]
[ 2.616] Current version of pixman: 0.32.4
[ 2.616] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 2.616] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2.616] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Apr 14 22:09:08 2014
[ 2.624] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 2.624] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 2.627] (==) No Layout section. Using the first Screen section.
[ 2.627] (==) No screen section available. Using defaults.
[ 2.627] (**) |-->Screen "Default Screen Section" (0)
[ 2.627] (**) | |-->Monitor "<default monitor>"
[ 2.628] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 2.628] (==) Automatically adding devices
[ 2.628] (==) Automatically enabling devices
[ 2.628] (==) Automatically adding GPU devices
[ 2.638] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 2.638] Entry deleted from font path.
[ 2.638] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 2.638] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 2.638] Entry deleted from font path.
[ 2.638] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 2.638] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/
[ 2.638] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 2.638] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 2.638] (II) Loader magic: 0x804c80
[ 2.638] (II) Module ABI versions:
[ 2.638] X.Org ANSI C Emulation: 0.4
[ 2.638] X.Org Video Driver: 15.0
[ 2.638] X.Org XInput driver : 20.0
[ 2.638] X.Org Server Extension : 8.0
[ 2.639] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 3.588] (--) PCI:*(0:0:2:0) 8086:0166:17aa:21f5 rev 9, Mem @ 0xf1400000/4194304, 0xe0000000/268435456, I/O @ 0x00006000/64
[ 3.588] (--) PCI: (0:1:0:0) 10de:0ffb:17aa:21f5 rev 161, Mem @ 0xf0000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00005000/128, BIOS @ 0x????????/524288
[ 3.588] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 3.589] Initializing built-in extension Generic Event Extension
[ 3.589] Initializing built-in extension SHAPE
[ 3.589] Initializing built-in extension MIT-SHM
[ 3.589] Initializing built-in extension XInputExtension
[ 3.589] Initializing built-in extension XTEST
[ 3.589] Initializing built-in extension BIG-REQUESTS
[ 3.589] Initializing built-in extension SYNC
[ 3.589] Initializing built-in extension XKEYBOARD
[ 3.589] Initializing built-in extension XC-MISC
[ 3.589] Initializing built-in extension SECURITY
[ 3.589] Initializing built-in extension XINERAMA
[ 3.589] Initializing built-in extension XFIXES
[ 3.589] Initializing built-in extension RENDER
[ 3.589] Initializing built-in extension RANDR
[ 3.589] Initializing built-in extension COMPOSITE
[ 3.589] Initializing built-in extension DAMAGE
[ 3.589] Initializing built-in extension MIT-SCREEN-SAVER
[ 3.589] Initializing built-in extension DOUBLE-BUFFER
[ 3.589] Initializing built-in extension RECORD
[ 3.589] Initializing built-in extension DPMS
[ 3.589] Initializing built-in extension Present
[ 3.590] Initializing built-in extension DRI3
[ 3.590] Initializing built-in extension X-Resource
[ 3.590] Initializing built-in extension XVideo
[ 3.590] Initializing built-in extension XVideo-MotionCompensation
[ 3.590] Initializing built-in extension XFree86-VidModeExtension
[ 3.590] Initializing built-in extension XFree86-DGA
[ 3.590] Initializing built-in extension XFree86-DRI
[ 3.590] Initializing built-in extension DRI2
[ 3.590] (II) "glx" will be loaded by default.
[ 3.590] (II) LoadModule: "dri2"
[ 3.590] (II) Module "dri2" already built-in
[ 3.590] (II) LoadModule: "glamoregl"
[ 3.593] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[ 3.615] (II) Module glamoregl: vendor="X.Org Foundation"
[ 3.615] compiled for 1.15.0, module version = 0.6.0
[ 3.615] ABI class: X.Org ANSI C Emulation, version 0.4
[ 3.615] (II) LoadModule: "glx"
[ 3.617] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 3.618] (II) Module glx: vendor="X.Org Foundation"
[ 3.618] compiled for 1.15.0, module version = 1.0.0
[ 3.618] ABI class: X.Org Server Extension, version 8.0
[ 3.618] (==) AIGLX enabled
[ 3.618] Loading extension GLX
[ 3.618] (==) Matched intel as autoconfigured driver 0
[ 3.618] (==) Matched intel as autoconfigured driver 1
[ 3.618] (==) Matched modesetting as autoconfigured driver 2
[ 3.618] (==) Matched fbdev as autoconfigured driver 3
[ 3.618] (==) Matched vesa as autoconfigured driver 4
[ 3.618] (==) Assigned the driver to the xf86ConfigLayout
[ 3.618] (II) LoadModule: "intel"
[ 3.618] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 3.623] (II) Module intel: vendor="X.Org Foundation"
[ 3.623] compiled for 1.15.0, module version = 2.99.911
[ 3.623] Module class: X.Org Video Driver
[ 3.623] ABI class: X.Org Video Driver, version 15.0
[ 3.623] (II) LoadModule: "modesetting"
[ 3.624] (WW) Warning, couldn't open module modesetting
[ 3.624] (II) UnloadModule: "modesetting"
[ 3.624] (II) Unloading modesetting
[ 3.624] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 3.624] (II) LoadModule: "fbdev"
[ 3.624] (WW) Warning, couldn't open module fbdev
[ 3.624] (II) UnloadModule: "fbdev"
[ 3.624] (II) Unloading fbdev
[ 3.624] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 3.624] (II) LoadModule: "vesa"
[ 3.624] (WW) Warning, couldn't open module vesa
[ 3.624] (II) UnloadModule: "vesa"
[ 3.624] (II) Unloading vesa
[ 3.624] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 3.624] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 3.624] (II) intel: Driver for Intel(R) HD Graphics: 2000-5000
[ 3.624] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100
[ 3.624] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200
[ 3.624] (++) using VT number 1
[ 3.625] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 4000
[ 3.625] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx
[ 3.625] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 3.625] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 3.625] (==) intel(0): RGB weight 888
[ 3.625] (==) intel(0): Default visual is TrueColor
[ 3.625] (**) intel(0): Framebuffer tiled
[ 3.625] (**) intel(0): Pixmaps tiled
[ 3.625] (**) intel(0): "Tear free" disabled
[ 3.625] (**) intel(0): Forcing per-crtc-pixmaps? no
[ 3.625] (II) intel(0): Output LVDS1 has no monitor section
[ 3.625] (--) intel(0): Found backlight control interface acpi_video0 (type 'firmware') for output LVDS1
[ 3.625] (II) intel(0): Output VGA1 has no monitor section
[ 3.625] (II) intel(0): Output VIRTUAL1 has no monitor section
[ 3.625] (--) intel(0): Output LVDS1 using initial mode 1920x1080 on pipe 0
[ 3.625] (==) intel(0): DPI set to (96, 96)
[ 3.625] (II) Loading sub module "dri2"
[ 3.625] (II) LoadModule: "dri2"
[ 3.625] (II) Module "dri2" already built-in
[ 3.625] (==) Depth 24 pixmap format is 32 bpp
[ 3.627] (II) intel(0): SNA initialized with Ivybridge (gen7, gt2) backend
[ 3.627] (==) intel(0): Backing store enabled
[ 3.627] (==) intel(0): Silken mouse enabled
[ 3.628] (II) intel(0): HW Cursor enabled
[ 3.628] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 3.628] (==) intel(0): DPMS enabled
[ 3.628] (II) intel(0): [DRI2] Setup complete
[ 3.628] (II) intel(0): [DRI2] DRI driver: i965
[ 3.628] (II) intel(0): [DRI2] VDPAU driver: i965
[ 3.628] (II) intel(0): direct rendering: DRI2 Enabled
[ 3.628] (==) intel(0): hotplug detection: "enabled"
[ 3.628] (--) RandR disabled
[ 3.650] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 3.650] (II) AIGLX: enabled GLX_ARB_create_context
[ 3.650] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 3.650] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 3.650] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 3.650] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 3.650] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 3.650] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 3.650] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 3.650] (II) AIGLX: Loaded and initialized i965
[ 3.650] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 3.652] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 3.665] (II) intel(0): Setting screen physical size to 508 x 285
[ 3.732] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 3.732] (**) Power Button: Applying InputClass "system-keyboard"
[ 3.732] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 3.732] (II) LoadModule: "evdev"
[ 3.732] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 3.734] (II) Module evdev: vendor="X.Org Foundation"
[ 3.734] compiled for 1.15.0, module version = 2.8.2
[ 3.734] Module class: X.Org XInput Driver
[ 3.734] ABI class: X.Org XInput driver, version 20.0
[ 3.734] (II) Using input driver 'evdev' for 'Power Button'
[ 3.734] (**) Power Button: always reports core events
[ 3.734] (**) evdev: Power Button: Device: "/dev/input/event3"
[ 3.734] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 3.734] (--) evdev: Power Button: Found keys
[ 3.734] (II) evdev: Power Button: Configuring as keyboard
[ 3.734] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event3"
[ 3.734] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 3.734] (**) Option "xkb_rules" "evdev"
[ 3.734] (**) Option "xkb_model" "pc104"
[ 3.734] (**) Option "xkb_layout" "se"
[ 3.754] (II) config/udev: Adding input device Video Bus (/dev/input/event13)
[ 3.754] (**) Video Bus: Applying InputClass "system-keyboard"
[ 3.754] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 3.754] (II) Using input driver 'evdev' for 'Video Bus'
[ 3.754] (**) Video Bus: always reports core events
[ 3.754] (**) evdev: Video Bus: Device: "/dev/input/event13"
[ 3.754] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 3.754] (--) evdev: Video Bus: Found keys
[ 3.754] (II) evdev: Video Bus: Configuring as keyboard
[ 3.754] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input15/event13"
[ 3.754] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 3.754] (**) Option "xkb_rules" "evdev"
[ 3.754] (**) Option "xkb_model" "pc104"
[ 3.754] (**) Option "xkb_layout" "se"
[ 3.754] (II) config/udev: Adding input device Video Bus (/dev/input/event14)
[ 3.754] (**) Video Bus: Applying InputClass "system-keyboard"
[ 3.754] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 3.754] (II) Using input driver 'evdev' for 'Video Bus'
[ 3.754] (**) Video Bus: always reports core events
[ 3.754] (**) evdev: Video Bus: Device: "/dev/input/event14"
[ 3.754] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 3.754] (--) evdev: Video Bus: Found keys
[ 3.754] (II) evdev: Video Bus: Configuring as keyboard
[ 3.754] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/LNXVIDEO:01/input/input16/event14"
[ 3.754] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
[ 3.754] (**) Option "xkb_rules" "evdev"
[ 3.754] (**) Option "xkb_model" "pc104"
[ 3.754] (**) Option "xkb_layout" "se"
[ 3.755] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
[ 3.755] (II) No input driver specified, ignoring this device.
[ 3.755] (II) This device may have been added with another device file.
[ 3.755] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
[ 3.755] (**) Sleep Button: Applying InputClass "system-keyboard"
[ 3.755] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 3.755] (II) Using input driver 'evdev' for 'Sleep Button'
[ 3.755] (**) Sleep Button: always reports core events
[ 3.755] (**) evdev: Sleep Button: Device: "/dev/input/event2"
[ 3.755] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 3.755] (--) evdev: Sleep Button: Found keys
[ 3.755] (II) evdev: Sleep Button: Configuring as keyboard
[ 3.755] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3/event2"
[ 3.755] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
[ 3.755] (**) Option "xkb_rules" "evdev"
[ 3.755] (**) Option "xkb_model" "pc104"
[ 3.755] (**) Option "xkb_layout" "se"
[ 3.755] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 3.755] (II) config/udev: Adding input device Integrated Camera (/dev/input/event6)
[ 3.756] (**) Integrated Camera: Applying InputClass "system-keyboard"
[ 3.756] (**) Integrated Camera: Applying InputClass "evdev keyboard catchall"
[ 3.756] (II) Using input driver 'evdev' for 'Integrated Camera'
[ 3.756] (**) Integrated Camera: always reports core events
[ 3.756] (**) evdev: Integrated Camera: Device: "/dev/input/event6"
[ 3.756] (--) evdev: Integrated Camera: Vendor 0x4f2 Product 0xb2eb
[ 3.756] (--) evdev: Integrated Camera: Found keys
[ 3.756] (II) evdev: Integrated Camera: Configuring as keyboard
[ 3.756] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input8/event6"
[ 3.756] (II) XINPUT: Adding extended input device "Integrated Camera" (type: KEYBOARD, id 10)
[ 3.756] (**) Option "xkb_rules" "evdev"
[ 3.756] (**) Option "xkb_model" "pc104"
[ 3.756] (**) Option "xkb_layout" "se"
[ 3.756] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event7)
[ 3.756] (II) No input driver specified, ignoring this device.
[ 3.756] (II) This device may have been added with another device file.
[ 3.756] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event11)
[ 3.756] (II) No input driver specified, ignoring this device.
[ 3.756] (II) This device may have been added with another device file.
[ 3.756] (II) config/udev: Adding input device HDA Intel PCH Dock Mic (/dev/input/event10)
[ 3.756] (II) No input driver specified, ignoring this device.
[ 3.756] (II) This device may have been added with another device file.
[ 3.756] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event9)
[ 3.756] (II) No input driver specified, ignoring this device.
[ 3.756] (II) This device may have been added with another device file.
[ 3.757] (II) config/udev: Adding input device HDA Intel PCH Dock Headphone (/dev/input/event8)
[ 3.757] (II) No input driver specified, ignoring this device.
[ 3.757] (II) This device may have been added with another device file.
[ 3.757] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 3.757] (**) AT Translated Set 2 keyboard: Applying InputClass "system-keyboard"
[ 3.757] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 3.757] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 3.757] (**) AT Translated Set 2 keyboard: always reports core events
[ 3.757] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 3.757] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 3.757] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 3.757] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 3.757] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 3.757] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
[ 3.757] (**) Option "xkb_rules" "evdev"
[ 3.757] (**) Option "xkb_model" "pc104"
[ 3.757] (**) Option "xkb_layout" "se"
[ 3.757] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event12)
[ 3.757] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 3.757] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 3.757] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
[ 3.757] (II) LoadModule: "synaptics"
[ 3.757] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 3.758] (II) Module synaptics: vendor="X.Org Foundation"
[ 3.758] compiled for 1.15.0, module version = 1.7.4
[ 3.758] Module class: X.Org XInput Driver
[ 3.758] ABI class: X.Org XInput driver, version 20.0
[ 3.758] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 3.758] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 3.758] (**) Option "Device" "/dev/input/event12"
[ 3.783] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
[ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5470 (res 60)
[ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4498 (res 85)
[ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
[ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 3.783] (**) Option "TapButton1" "1"
[ 3.783] (**) Option "TapButton2" "2"
[ 3.783] (**) Option "TapButton3" "3"
[ 3.783] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 3.783] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 3.793] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event12"
[ 3.793] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 12)
[ 3.793] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 3.793] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
[ 3.793] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.040
[ 3.793] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 3.793] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 3.793] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 3.793] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 3.793] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 3.793] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[ 3.793] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
[ 3.794] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
[ 3.794] (II) No input driver specified, ignoring this device.
[ 3.794] (II) This device may have been added with another device file.
[ 3.794] (II) config/udev: Adding input device ThinkPad Extra Buttons (/dev/input/event4)
[ 3.794] (**) ThinkPad Extra Buttons: Applying InputClass "system-keyboard"
[ 3.794] (**) ThinkPad Extra Buttons: Applying InputClass "evdev keyboard catchall"
[ 3.794] (II) Using input driver 'evdev' for 'ThinkPad Extra Buttons'
[ 3.794] (**) ThinkPad Extra Buttons: always reports core events
[ 3.794] (**) evdev: ThinkPad Extra Buttons: Device: "/dev/input/event4"
[ 3.794] (--) evdev: ThinkPad Extra Buttons: Vendor 0x17aa Product 0x5054
[ 3.794] (--) evdev: ThinkPad Extra Buttons: Found keys
[ 3.795] (II) evdev: ThinkPad Extra Buttons: Configuring as keyboard
[ 3.795] (**) Option "config_info" "udev:/sys/devices/platform/thinkpad_acpi/input/input5/event4"
[ 3.795] (II) XINPUT: Adding extended input device "ThinkPad Extra Buttons" (type: KEYBOARD, id 13)
[ 3.795] (**) Option "xkb_rules" "evdev"
[ 3.795] (**) Option "xkb_model" "pc104"
[ 3.795] (**) Option "xkb_layout" "se"
[ 3.799] (II) config/udev: removing device SynPS/2 Synaptics TouchPad
[ 3.824] (II) UnloadModule: "synaptics"
[ 3.824] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event12)
[ 3.824] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 3.824] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 3.824] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
[ 3.824] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 3.824] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 3.824] (**) Option "Device" "/dev/input/event12"
[ 3.844] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
[ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5470 (res 60)
[ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4498 (res 85)
[ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
[ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 3.844] (**) Option "TapButton1" "1"
[ 3.844] (**) Option "TapButton2" "2"
[ 3.844] (**) Option "TapButton3" "3"
[ 3.844] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 3.844] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 3.854] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event12"
[ 3.854] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 12)
[ 3.854] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 3.854] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
[ 3.854] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.040
[ 3.854] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 3.854] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 3.854] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 3.854] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 3.854] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 3.854] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[ 3.854] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
[ 3.855] removing GPU device /sys/devices/pci0000:00/0000:00:02.0/drm/card0 /dev/dri/card0
[ 3.855] xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
[ 3.855] failed to find screen to remove
[ 3.855] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 3.855] removing GPU device /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1 (null)
[ 3.855] (II) config/udev: removing device Video Bus
[ 3.863] (II) evdev: Video Bus: Close
[ 3.863] (II) UnloadModule: "evdev"
[ 3.863] (II) config/udev: Adding input device Video Bus (/dev/input/event13)
[ 3.863] (**) Video Bus: Applying InputClass "system-keyboard"
[ 3.863] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 3.863] (II) Using input driver 'evdev' for 'Video Bus'
[ 3.863] (**) Video Bus: always reports core events
[ 3.863] (**) evdev: Video Bus: Device: "/dev/input/event13"
[ 3.863] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 3.863] (--) evdev: Video Bus: Found keys
[ 3.863] (II) evdev: Video Bus: Configuring as keyboard
[ 3.863] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input15/event13"
[ 3.863] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 3.863] (**) Option "xkb_rules" "evdev"
[ 3.863] (**) Option "xkb_model" "pc104"
[ 3.863] (**) Option "xkb_layout" "se"
[ 3.863] removing GPU device /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-VGA-1 (null)
[ 3.863] (II) config/udev: removing device Video Bus
[ 3.870] (II) evdev: Video Bus: Close
[ 3.870] (II) UnloadModule: "evdev"
[ 3.870] (II) config/udev: Adding input device Video Bus (/dev/input/event14)
[ 3.870] (**) Video Bus: Applying InputClass "system-keyboard"
[ 3.870] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 3.870] (II) Using input driver 'evdev' for 'Video Bus'
[ 3.870] (**) Video Bus: always reports core events
[ 3.870] (**) evdev: Video Bus: Device: "/dev/input/event14"
[ 3.870] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 3.870] (--) evdev: Video Bus: Found keys
[ 3.870] (II) evdev: Video Bus: Configuring as keyboard
[ 3.870] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/LNXVIDEO:01/input/input16/event14"
[ 3.870] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
[ 3.870] (**) Option "xkb_rules" "evdev"
[ 3.870] (**) Option "xkb_model" "pc104"
[ 3.870] (**) Option "xkb_layout" "se"
[ 4.540] (II) intel(0): EDID vendor "LEN", prod id 16562
[ 4.540] (II) intel(0): Printing DDC gathered Modelines:
[ 4.540] (II) intel(0): Modeline "1920x1080"x0.0 139.00 1920 1980 2028 2050 1080 1090 1100 1130 -hsync -vsync (67.8 kHz eP)
[ 4.540] (II) intel(0): Modeline "1920x1080"x0.0 115.83 1920 1980 2028 2050 1080 1090 1100 1130 -hsync -vsync (56.5 kHz e)
[ 7.358] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/event15)
[ 7.358] (**) TPPS/2 IBM TrackPoint: Applying InputClass "evdev pointer catchall"
[ 7.358] (**) TPPS/2 IBM TrackPoint: Applying InputClass "Trackpoint Wheel Emulation"
[ 7.358] (II) Using input driver 'evdev' for 'TPPS/2 IBM TrackPoint'
[ 7.358] (**) TPPS/2 IBM TrackPoint: always reports core events
[ 7.358] (**) evdev: TPPS/2 IBM TrackPoint: Device: "/dev/input/event15"
[ 7.358] (--) evdev: TPPS/2 IBM TrackPoint: Vendor 0x2 Product 0xa
[ 7.358] (--) evdev: TPPS/2 IBM TrackPoint: Found 3 mouse buttons
[ 7.358] (--) evdev: TPPS/2 IBM TrackPoint: Found relative axes
[ 7.358] (--) evdev: TPPS/2 IBM TrackPoint: Found x and y relative axes
[ 7.358] (II) evdev: TPPS/2 IBM TrackPoint: Configuring as mouse
[ 7.358] (**) Option "Emulate3Buttons" "false"
[ 7.358] (**) Option "EmulateWheel" "true"
[ 7.358] (**) Option "EmulateWheelButton" "2"
[ 7.358] (**) Option "YAxisMapping" "4 5"
[ 7.358] (**) evdev: TPPS/2 IBM TrackPoint: YAxisMapping: buttons 4 and 5
[ 7.358] (**) Option "XAxisMapping" "6 7"
[ 7.358] (**) evdev: TPPS/2 IBM TrackPoint: XAxisMapping: buttons 6 and 7
[ 7.358] (**) evdev: TPPS/2 IBM TrackPoint: EmulateWheelButton: 2, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 7.358] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/serio2/input/input14/event15"
[ 7.358] (II) XINPUT: Adding extended input device "TPPS/2 IBM TrackPoint" (type: MOUSE, id 14)
[ 7.358] (II) evdev: TPPS/2 IBM TrackPoint: initialized for relative axes.
[ 7.359] (**) TPPS/2 IBM TrackPoint: (accel) keeping acceleration scheme 1
[ 7.359] (**) TPPS/2 IBM TrackPoint: (accel) acceleration profile 0
[ 7.359] (**) TPPS/2 IBM TrackPoint: (accel) acceleration factor: 2.000
[ 7.359] (**) TPPS/2 IBM TrackPoint: (accel) acceleration threshold: 4
[ 7.359] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/mouse1)
[ 7.359] (II) No input driver specified, ignoring this device.
[ 7.359] (II) This device may have been added with another device file.
[ 20245.335] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 21030.923] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 21196.939] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 21209.255] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 24416.533] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 26177.657] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none -
No image on screen using Mini DisplayPort to VGA Adapter
Received mini today. After unboxing, read through the packet. Then began to hook everything up as directed. I used a Mini DisplayPort to VGA Adapter to connect the monitor from our now dead desktop to the mini. After double checking all connections, I hit the power button. I immediately heard the apple chime. Then the monitor showed the grey apple start up screen. Suddenly the monitor went black and said it was going into sleep mode. I can't get it out of sleep mode when connected to the mini. It is NOT the monitor or the adapter. I plugged the monitor straight into a netbook and it worked. Then, I plugged the monitor using the adapter into my MacBook Pro and also got it to work that way. So I tried replugging the adapter into the mini. Still can't get an image on the screen. I can't complete set up or use mini because I can't get an image. Any suggestions or ideas? I will call apple in the morning if I can't figure it out tonight. But I'm hoping someone can give me suggestions. Thanks for your help!
I had the same issue when I bought my mac mini last week apart from I wasn't even getting the initial grey screen. I went back to the Apple shop and they gave me another mini and fired it up in the shop using the adaptor on an old VGA monitor. It worked perfectly.
When I got home I set it all up again and still had the same issue. I nearly threw out a couple of monitors as I thought they were broken.
However, had a look around the web and found this suggestion:
Shut down the mac and disconnect the adaptor from it. Now fire the mac up and let it boot up FULLY. Once it has had a chance to boot up fully, only then plug the adaptor in.
Worked for me and I haven't had the issue since (touch wood). Hope this helps. -
Mini DisplayPort to VGA Adapter problems
I connected my Apple Pro to my HD TV to watch streamed movies on my computer using the TV as a monitor. I was advised to purchase a Mini DisplayPort to VGA Adapter and all the connections fit. The first time I connected it was no problem. I watched the movie and the audio was fine. Then the 2nd time I connected I had no screen. It was a blue wavy screen on the TV, even though the computer screen was showing the show. I believe it may have been showing me some sort of screensaver application from what i've read on the forums but I have no idea why or how. Then the next day I tried again. The screen was fine but the audio quality was terrible. It was like listening through a cheap radio. Why am I having so many problems and the quality is not consistent. Are there settings I should change when I do this?
I have some good news.
Regarding the broken lines on the output of the Mini DisplayPort, it seems as though it "fixed" itself. My theory is, I recently installed Windows 7. Updated all the drivers on the windows side and got it to project properly with the new Intel 4000 graphic cards. Once that happened, it kind of "popped the cherry" on the port and now both Mac and Windows output properly through the Mini DisplayPort.
I've tested it with numerous adapters and once it outputed properly for the first time ever, all subsequent times work.
I now have tested in on LCD and DLP projectors, Philips monitors, Skyworth TVs, Sanyo TVs.
It's working with the Mini DisplayPort - VGA adapter.
It's also working with the Mini DisplayPort - DVI adapter as well.
Before I "popped the cherry" on the output port, nothing else worked. 1440x900 didn't work, neither did mirroring the displays. It just had to work once with whatever OS and after that it outputs fine all the time.
If you ahve the same problem as above, i'd recommend dual booting another OS, load the proper graphix drivers, get it to output properly once and hopefully it'll fix the problem like it did for my unit.
Thanks for everyone's input with the whole ordeal!
PS. after the initial output, it didn't matter which adapter I used. I kept the generic since it's cheaper, returned the apple one cuz it's exactly the same, and now bought a generic MiniDP - DVI for my at home workstation.
PPS. One final picture of it working.... -
Connecting my macbook pro 13" to Sony bravia via mini Displayport to HDMI
Hi,
yesterday I bought a new LCD TV Sony Bravia KDL-32EX600 (Full-HD LED) that has 4 x HDMI inputs.
I also bought a mini Displayport to HDMI and HDMI to HDMI cable.
When I connect it to my computer, the screen goes blue for a second and it doesn't recognise any additional displays. There's also no video or sound in the TV, on the right HDMI channel. (I've tried every HDMI input and every channel)
I've tested the TV with another laptop that has straight HDMI output from the gfx card and it works perfectly.
I have up-to-date MacOS and I also upgraded my TV's firmware to the latest.
I thought that maybe the miniDisplayport to HDMI connector is broken but why does the computer try to do something when I turn on the correct channel on the TV?
I'm out of ideas..Hi madhenry,
I know it's a month on from your post, but I thought I'd add that I'm having exactly the same problem. I'm trying to connect my new MacBook Pro (15" core i7) to my Sony Bravia KDL-40EX600 using a mini displayport to HDMI adapter. When I plug the cable in, the MBP screen goes blue for one second then goes back to normal, but the system just doesn't detect the external display.
I've tried the MBP on other monitors and it works fine, so there is nothing wrong with the adapter or cable.
I've also tried plugging two other Macs into the TV (a 2008 15" MacBook Pro and a 2008 MacBook) and the TV works great with both of them.
So, it seems there's something specific to the new MacBook Pros that makes them incompatible with the Sony EX600 TVs.
I just talked to AppleCare about it and after trying a few things (resetting the PRAM, etc.) I was simply told that there's nothing wrong at all with the Mac and that this is simply a "compatibility" issue that I have to put up with. So, it looks like we're out of luck until (hopefully) a new Mac OS update fixes the issue.
Peter -
Mini Displayport to HDMI Adapter - Sound?
I have hooked up my mini by the Mini Displayport to HDMI adapter to my Philips FlatTV. Sound is only played by the internal mini speaker, not from TV.
According Apple Support the sound should be working on the TV when using the adapter. They reckon my adapter is broken.
I know that there is no sound from the Minidvi to HDMI adapter unless you use external audio cable, but with the Mini Displayport?
Has anyone actually managed to make this work?
Thanks!As already pointed out in this thread, Apple currently do not support routing audio out via the Mini Displayport connector even though the Displayport specifications allow for this. Therefore a 'standard' Mini Displayport to HDMI adapter will not be able to provide audio since the Mac will not be sending it.
However many people have been disappointed with Apple's omission and as a result at least one manufacturer of adapters has developed a solution to workaround this.
If you look at http://www.monoprice.com/products/product.asp?cid=104&cp_id=10428&cs_id=1042802&pid=5311&seq=1&format=2 you will see the 'standard' style Mini Displayport to HDMI adapter which due to Apple, does not currently provide audio. If you however look at this model http://www.monoprice.com/products/product.asp?cid=104&cp_id=10428&cs_id=1042802&pid=6331&seq=1&format=2 then it gets round the problem by connecting to both the Mini Displayport on a Mac and the Mac's Mini TOS-Link digital output and then 'merges' them together before sending them out via a single HDMI cable. This would therefore provide audio to your TV. -
T430 1600x900 i5 Core: Mini DisplayPort To HDMI 1920x1080 TV Resolution And Sizing-Overscan Problems
Hello, and thanks in advance for any help. Also, my apologies if these issues have been previously resolved; I've spent 2 days searching for answers and none of my effort has resulted in a solution, either here or elsewhere.
I very recently for the first time connected my ThinkPad T430 2344-5GU (i5 core, native screen resolution 1600x900, Intel HD 4000 v9.17.10.2843, NVIDIA Optimus NVS 5400M v9.18.13.1100) to a Panasonic HD TV (native screen resolution 1920x1080) using a Mini DisplayPort to HDMI connector, with the hope of playing 1080p movies on my laptop while watching them on the TV. This seemingly worked fine at first--both audio and video were present--but I quickly noticed that the image on the TV was, very slightly, larger than the image on the laptop screen (cutting off roughly 5% of the image on each of the 4 sides) and that the resolution wasn't 1920x1080. So I hunted for a solution.
Windows display properties were no help. In fact, as soon as I tweaked something there I lost the picture on the TV (the options available are "Show desktop only on 1" (the laptop screen), "Show desktop only on 2" (the TV screen), and "Extend these screens", which annoyingly turns the TV blank yet allows the cursor to to enter the TV screen depending on the chosen layout and the cursor's approach direction to the TV). So, from having a functional-if-slightly-oversized-and-lower-quality picture on the TV screen I went to nothing, at least for my desired use.
Further research led me to the Intel HD 4000 settings, but those didn't even show that multiple screens were in use when the TV is attached. Finally, I tried using the NVIDEA Control Panel, but although multiple displays seem to be supported the best I can do when cloning is have the screens' resolutions meet in the middle at 1440x900, which makes them both look worse than the original plug-and-play result described above. Heck, I went so far as to enter the BIOS and try every combination possible under "Graphics": no NVIDEA, Integrated, Discrete, each with and without "Auto Detect NVIDEA capability" enabled and disabled. I even updated the NVIDEA driver to their newest, a version not available at the Lenovo Support site. Nothing. And worse, ever since my very first tweak under Windows display properties I wasn't able to return to the original functional-if-slightly-oversized-and-lower-quality picture.
At this point I used a very recent image to return my system to it's Pre Original Tweak state (allowing for the functional-if-slightly-oversized-and-lower-quality picture originally obtained), which is better than nothing, I guess, but surely not what I'd expect from a higher end laptop.
Please, does anyone know if there's a way to connect my T430, native resolution 1600x900, to an HD TV, native resolution 1920x1080, while actually maintaining each screens respective native resolution and not losing any of the image? Thank you again for your time.
Edit: After more research I've fit the desktop image to the screen by adjusting the TV's "Picture/Advanced picture/HD size" setting from "Size 1" to "Size 2". Now my only question is if it's possible to somehow play a 1080p movie at the TV's native resolution of 1920x1080 or if I'm stuck with the laptop's navtive resolution of 1600x900.Try grabbing the latest NVIDIA driver off of the NVIDIA website. It might help.
Extending it should also allow you to run the 1600x900 T430 screen plus the 1920x1080 TV screen each at their native resolutions.
W520: i7-2720QM, Q2000M at 1080/688/1376, 21GB RAM, 500GB + 750GB HDD, FHD screen
X61T: L7500, 3GB RAM, 500GB HDD, XGA screen, Ultrabase
Y3P: 5Y70, 8GB RAM, 256GB SSD, QHD+ screen -
Lenovo X1 mini-Displayport to VGA not working
Hi,
i recently needed to re-install a Lenovo X1, but i didn't have a Lenovo Windows-7-Image, so i used another one instead.
After installing, i updated all the drivers, using the ones provided on this page: http://support.lenovo.com/de/de/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x1
Unfortunately, the mini-Displayport does not seem to work. I tried to connect a mDP-VGA-Adapter, to connect it to a beamer and it didn't work, neither did it with another adapter.
Also i tried connecting it to a TV, also didn't work.
Any help how i could solve this problem?This is the Mac Pro desktop forum. I requested your post be moved to the MacBook Pro laptop forum.
-
X1 Carbon mini Displayport won't connect toHDMI
Hi I have an X1 carbon type 3443 thinkpadand while the mini displayport will now connect via a VGA adapter without intermittently going to a black screen following updating the BIOS with the Dec 2013 update, it will not connect to a HDMI screen at all. Windows 8.1 64bit
The external HDMI screen is not shown in Control Panel/Display/Screen Resolution and Fn F7 goes nowhere.
Any ideas on what I should try next before asking for a refund?Hi BenZion,
Welcome to Lenovo Community!
As per the query we understood that you are facing the issue with Display port on your ThinkPad X1 Carbon.
Have you checked with updating Graphic drivers and BIOS update?
If you have any difficulty in finding the drivers, please share the MTM number & OS (Operating System) of your device so that I can assist you with the drivers.
Hope this helps!
Best regards
Hemanth Kumar.B
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! -
Mini displayport wont work ANYMORE?.
Hey all.
About a year ago I bought a mini displayport to HDMI adapter, and it worked fine. But then it began to only work sometimes. And now it wont work at all.
Sometimes I try to plug it in and then pull slightly to one and the other side, and sometimes a picture actually accurs on my external screen - whick got me thinking that the problem must be a loose connection or something?
My question here is: Do u think that it is the adapter or the port?.. Has anyone ever experienced a broken Mini displayport?..
(it is a Moshi adapter, and it looks like new on the outside..)the serial number is CNF74741T0
-
Lenovo ThinkPad Helix Mini DisplayPort Monitor not Detected
My ThinkPad Helix does not detect the connection of a known good Mini DisplayPort to VGA adapter, VGA cable, and monitor.
Windows 8.1 Pro
Intel HD Graphics 4000 Driver 10.18.10.3958
Thanks for any troubleshooting tips.Hi, Backupsonline
Before buying another adapter, I would just make sure that the system is fully up to date by means of drivers and BIOS. Here is the driver matrix for your machine, which lists all available updates for the system. Try downloading the latest versions for your devices and see if it helps.
Best,
Adam
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.
Maybe you are looking for
-
How do I update the software on my iPad to iOS 6.3.1?
How do I update the software on my iPad to iOS 6.3.1 from iOS 5.1.1?
-
How to get the number of processor license
Hi, SQL> select CPU_COUNT_CURRENT,CPU_CORE_COUNT_CURRENT,CPU_COUNT_HIGHWATER,CPU_CORE_COUNT_HIGHWATER,CPU_SOCKET_COUNT_HIGHWATER 2 from v$license; CPU_COUNT_CURRENT CPU_CORE_COUNT_CURRENT CPU_COUNT_HIGHWATER CPU_CORE_COUNT_HIGHWATER CPU_SOCKET_COUNT_
-
Help - I'm a newbie to Mac and still need my Internet Explorer browser!
macbook pro Mac OS X (10.4.8) Hi - I just purchased a macbook pro and am in the process of designing a website - after encountering problem after problem, the hosting company figured out that I'm using a Mac, and said that their program doesn't s
-
SQL Reporting Services report hyperlink error
I have an issue were experiencing with SQL SCCM Reporting Services When we run reports in SQL RS and the reports have are able to be drilled into detail by selecting the eg. computer name we find that we get the following issue. "The item '/ConfigMgr
-
Has anyone else had problems since downloading latest update? My iTunes stopped working and mobile device won't download, I now don't have Apple to backup my iphone?