ThinkPad W530 - Boot with fingerprint
Hi everybody !
I saw this video on YouTube : http://www.youtube.com/watch?v=mQ-CxzO5CRk
At 0:45", the guy starts his W530 by swyping his thumb on the fingerprint reader.
How can I configure the laptop to make the same ?
Thank you.
soon W530|i7 3720QM|16GB|K2000M|240GB SSD|500GB 5400rpm
Assuming you have a fingerprint reader with your fingerprints enrolled, this is how I would set it up on my W520 running Windows 7. You could see if it will work with your W530.
1. Access "ThinkVantage Fingerprint Software" console. Two ways to do this. One is to go to Control Panel and click on User Accounts and Family Safety. When you have the User Accounts window open, look to the list on the shaded panel on the left, the item at the bottom is "Manage your fingerprint data." Click on this, it brings you to the Fingerprint console.
Another way to do this is to choose "Lenovo Device Experience." It may be in your start menu or programs list. Under "Lenovo ThinkVantage Tools," choose "Fingerprint Reader."
2. When you open the Fingerprint Software console, you will first see a schematic of the fingerprints you have registered. Across the black bar at the top of the Window, you'll see "Settings" as the third option. Choose Settings.
3. In fingerprint settings, you'll see the options you're looking for. The first one is "use fingerprint scan instead of password when logging into windows" under the Heading "Windows Authentication." You can decide if you want this or not.
Under the Heading "Power On Security" is the option you're looking for: "Use fingerprint scan instead of power-on button." On my system, I also chose the item beneath this, "enable single sign-on capability."
That should set it up for you.
W520 4270CTO: i7-2760QM, 16GB RAM, Samsung 830 Series SSD 256GB, Quadro 1000M, Centrino Ultimate-N 6300
Similar Messages
-
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 -
[SOLVED] Bumblebee: Failed to initialize GPU with Lenovo ThinkPad W530
SOLVED: See post #20
After years, I decided to come back to the wonderful distro, Arch and back to the forums. Yay!
However, I installed Arch to my new laptop - Lenovo ThinkPad W530 and it uses NVIDIA Quadro K1000M alongside Intel graphics with Optimus technology. Arch is running fine, but I cannot run applications through optirun and I get:
[exitium@rambutan ~]$ optirun -vv nvidia-settings
[ 485.536478] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
[ 485.536909] [DEBUG]optirun version 3.2.1 starting...
[ 485.536922] [DEBUG]Active configuration:
[ 485.536927] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
[ 485.536931] [DEBUG] X display: :8
[ 485.536934] [DEBUG] LD_LIBRARY_PATH: /usr/lib/nvidia:/usr/lib32/nvidia
[ 485.536938] [DEBUG] Socket path: /var/run/bumblebee.socket
[ 485.536941] [DEBUG] Accel/display bridge: auto
[ 485.536945] [DEBUG] VGL Compression: proxy
[ 485.536948] [DEBUG] VGLrun extra options:
[ 485.536952] [DEBUG] Primus LD Path: /usr/lib/primus:/usr/lib32/primus
[ 485.536972] [DEBUG]Using auto-detected bridge virtualgl
[ 485.537190] [INFO]Response: No - error: [XORG] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
[ 485.537204] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
[ 485.537209] [DEBUG]Socket closed.
[ 485.537223] [ERROR]Aborting because fallback start is disabled.
[ 485.537229] [DEBUG]Killing all remaining processes.
As seen, it says "Failed to initialize the NVIDIA GPU". I have tried different solutions found from these forums and several other places but none of them have worked - the problem remains same. Does anyone have idea how I could fix this? I read somewhere else that there could be issues with newest nvidia drivers - is this possible?
bumblebee.conf:
# Configuration file for Bumblebee. Values should **not** be put between quotes
## Server options. Any change made in this section will need a server restart
# to take effect.
[bumblebeed]
# The secondary Xorg server DISPLAY number
VirtualDisplay=:8
# Should the unused Xorg server be kept running? Set this to true if waiting
# for X to be ready is too long and don't need power management at all.
KeepUnusedXServer=false
# The name of the Bumbleblee server group name (GID name)
ServerGroup=bumblebee
# Card power state at exit. Set to false if the card shoud be ON when Bumblebee
# server exits.
TurnCardOffAtExit=false
# The default behavior of '-f' option on optirun. If set to "true", '-f' will
# be ignored.
NoEcoModeOverride=false
# The Driver used by Bumblebee server. If this value is not set (or empty),
# auto-detection is performed. The available drivers are nvidia and nouveau
# (See also the driver-specific sections below)
Driver=
# Directory with a dummy config file to pass as a -configdir to secondary X
XorgConfDir=/etc/bumblebee/xorg.conf.d
## Client options. Will take effect on the next optirun executed.
[optirun]
# Acceleration/ rendering bridge, possible values are auto, virtualgl and
# primus.
Bridge=auto
# The method used for VirtualGL to transport frames between X servers.
# Possible values are proxy, jpeg, rgb, xv and yuv.
VGLTransport=proxy
# List of paths which are searched for the primus libGL.so.1 when using
# the primus bridge
PrimusLibraryPath=/usr/lib/primus:/usr/lib32/primus
# Should the program run under optirun even if Bumblebee server or nvidia card
# is not available?
AllowFallbackToIGC=false
# Driver-specific settings are grouped under [driver-NAME]. The sections are
# parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
# detection resolves to NAME).
# PMMethod: method to use for saving power by disabling the nvidia card, valid
# values are: auto - automatically detect which PM method to use
# bbswitch - new in BB 3, recommended if available
# switcheroo - vga_switcheroo method, use at your own risk
# none - disable PM completely
# https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods
## Section with nvidia driver specific options, only parsed if Driver=nvidia
[driver-nvidia]
# Module name to load, defaults to Driver if empty or unset
KernelDriver=nvidia
PMMethod=auto
# colon-separated path to the nvidia libraries
LibraryPath=/usr/lib/nvidia:/usr/lib32/nvidia
# comma-separated path of the directory containing nvidia_drv.so and the
# default Xorg modules path
XorgModulePath=/usr/lib/nvidia/xorg/,/usr/lib/xorg/modules
XorgConfFile=/etc/bumblebee/xorg.conf.nvidia
## Section with nouveau driver specific options, only parsed if Driver=nouveau
[driver-nouveau]
KernelDriver=nouveau
PMMethod=auto
XorgConfFile=/etc/bumblebee/xorg.conf.nouveau
xorg.conf.nvidia
Section "ServerLayout"
Identifier "Layout0"
Option "AutoAddDevices" "false"
Option "AutoAddGPU" "false"
Option "UseDisplayDevice" "none"
EndSection
Section "Device"
Identifier "DiscreteNvidia"
Driver "nvidia"
VendorName "NVIDIA Corporation"
# If the X server does not automatically detect your VGA device,
# you can manually set it here.
# To get the BusID prop, run `lspci | egrep 'VGA|3D'` and input the data
# as you see in the commented example.
# This Setting may be needed in some platforms with more than one
# nvidia card, which may confuse the proprietary driver (e.g.,
# trying to take ownership of the wrong device). Also needed on Ubuntu 13.04.
BusID "PCI:01:00:0"
# Setting ProbeAllGpus to false prevents the new proprietary driver
# instance spawned to try to control the integrated graphics card,
# which is already being managed outside bumblebee.
# This option doesn't hurt and it is required on platforms running
# more than one nvidia graphics card with the proprietary driver.
# (E.g. Macbook Pro pre-2010 with nVidia 9400M + 9600M GT).
# If this option is not set, the new Xorg may blacken the screen and
# render it unusable (unless you have some way to run killall Xorg).
Option "ProbeAllGpus" "false"
Option "NoLogo" "true"
Option "UseEDID" "false"
Option "UseDisplayDevice" "none"
EndSection
Thank you in advance!
Last edited by Exitium (2013-12-18 11:29:54)Hi!
Exactly the same issue here. Notebook -> Thinkpad W530
Currently running on:
linux 3.11.3-1
nvidia 325.15-8
nvidia-utils 325.15-1
bbswitch 0.7-14
Error:
username@hostname ~ $ optirun -vv nvidia-settings
[ 839.449203] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
[ 839.449495] [INFO]Configured driver: nvidia
[ 839.449729] [DEBUG]optirun version 3.2.1 starting...
[ 839.449774] [DEBUG]Active configuration:
[ 839.449817] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
[ 839.449836] [DEBUG] X display: :8
[ 839.449856] [DEBUG] LD_LIBRARY_PATH: /usr/lib/nvidia:/usr/lib32/nvidia
[ 839.449875] [DEBUG] Socket path: /var/run/bumblebee.socket
[ 839.449890] [DEBUG] Accel/display bridge: auto
[ 839.449909] [DEBUG] VGL Compression: proxy
[ 839.449936] [DEBUG] VGLrun extra options:
[ 839.449953] [DEBUG] Primus LD Path: /usr/lib/primus:/usr/lib32/primus
[ 839.449996] [DEBUG]Using auto-detected bridge virtualgl
[ 839.450294] [INFO]Response: No - error: [XORG] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
[ 839.450344] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
[ 839.450373] [DEBUG]Socket closed.
[ 839.450398] [ERROR]Aborting because fallback start is disabled.
[ 839.450419] [DEBUG]Killing all remaining processes.
dmesg output:
[ 81.162604] bbswitch: enabling discrete graphics
[ 81.396637] pci 0000:01:00.0: power state changed by ACPI to D0
[ 81.396663] thinkpad_acpi: EC reports that Thermal Table has changed
[ 81.483200] nvidia: module license 'NVIDIA' taints kernel.
[ 81.483205] Disabling lock debugging due to kernel taint
[ 81.488096] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
[ 81.488289] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:01:00.0 on minor 1
[ 81.488294] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 325.15 Wed Jul 31 18:50:56 PDT 2013
[ 81.665938] nvidia 0000:01:00.0: irq 50 for MSI/MSI-X
[ 81.670434] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 81.670528] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 81.670594] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 81.670659] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 81.670723] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 81.670960] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 81.671192] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 81.671258] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.879826] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.905471] NVRM: GPU at 0000:01:00.0 has fallen off the bus.
[ 85.905479] NVRM: os_pci_init_handle: invalid context!
[ 85.905481] NVRM: os_pci_init_handle: invalid context!
[ 85.905486] NVRM: GPU at 0000:01:00.0 has fallen off the bus.
[ 85.905490] NVRM: os_pci_init_handle: invalid context!
[ 85.905491] NVRM: os_pci_init_handle: invalid context!
[ 85.930135] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.930442] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.930719] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.930990] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.931258] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.931526] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.931794] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.932062] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.932329] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.932595] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.932862] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.933129] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.933396] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.933662] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.933942] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.934197] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.934452] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.934706] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.934960] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.935215] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.935469] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.935722] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.935976] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[ 85.940508] NVRM: RmInitAdapter failed! (0x25:0x28:1157)
[ 85.940517] NVRM: rm_init_adapter(0) failed
xorg.conf.nvidia:
Section "ServerLayout"
Identifier "Layout0"
Option "AutoAddDevices" "false"
Option "AutoAddGPU" "false"
EndSection
Section "Device"
Identifier "DiscreteNvidia"
Driver "nvidia"
VendorName "NVIDIA Corporation"
# If the X server does not automatically detect your VGA device,
# you can manually set it here.
# To get the BusID prop, run `lspci | egrep 'VGA|3D'` and input the data
# as you see in the commented example.
# This Setting may be needed in some platforms with more than one
# nvidia card, which may confuse the proprietary driver (e.g.,
# trying to take ownership of the wrong device). Also needed on Ubuntu 13.04.
BusID "PCI:01:00:0"
# Setting ProbeAllGpus to false prevents the new proprietary driver
# instance spawned to try to control the integrated graphics card,
# which is already being managed outside bumblebee.
# This option doesn't hurt and it is required on platforms running
# more than one nvidia graphics card with the proprietary driver.
# (E.g. Macbook Pro pre-2010 with nVidia 9400M + 9600M GT).
# If this option is not set, the new Xorg may blacken the screen and
# render it unusable (unless you have some way to run killall Xorg).
Option "ProbeAllGpus" "false"
Option "NoLogo" "true"
Option "UseEDID" "false"
Option "UseDisplayDevice" "none"
EndSection
bumblebee.conf:
# Configuration file for Bumblebee. Values should **not** be put between quotes
## Server options. Any change made in this section will need a server restart
# to take effect.
[bumblebeed]
# The secondary Xorg server DISPLAY number
VirtualDisplay=:8
# Should the unused Xorg server be kept running? Set this to true if waiting
# for X to be ready is too long and don't need power management at all.
KeepUnusedXServer=false
# The name of the Bumbleblee server group name (GID name)
ServerGroup=bumblebee
# Card power state at exit. Set to false if the card shoud be ON when Bumblebee
# server exits.
TurnCardOffAtExit=false
# The default behavior of '-f' option on optirun. If set to "true", '-f' will
# be ignored.
NoEcoModeOverride=false
# The Driver used by Bumblebee server. If this value is not set (or empty),
# auto-detection is performed. The available drivers are nvidia and nouveau
# (See also the driver-specific sections below)
Driver=nvidia
# Directory with a dummy config file to pass as a -configdir to secondary X
XorgConfDir=/etc/bumblebee/xorg.conf.d
## Client options. Will take effect on the next optirun executed.
[optirun]
# Acceleration/ rendering bridge, possible values are auto, virtualgl and
# primus.
Bridge=auto
# The method used for VirtualGL to transport frames between X servers.
# Possible values are proxy, jpeg, rgb, xv and yuv.
VGLTransport=proxy
# List of paths which are searched for the primus libGL.so.1 when using
# the primus bridge
PrimusLibraryPath=/usr/lib/primus:/usr/lib32/primus
# Should the program run under optirun even if Bumblebee server or nvidia card
# is not available?
AllowFallbackToIGC=false
# Driver-specific settings are grouped under [driver-NAME]. The sections are
# parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
# detection resolves to NAME).
# PMMethod: method to use for saving power by disabling the nvidia card, valid
# values are: auto - automatically detect which PM method to use
# bbswitch - new in BB 3, recommended if available
# switcheroo - vga_switcheroo method, use at your own risk
# none - disable PM completely
# https://github.com/Bumblebee-Project/Bu … PM-methods
## Section with nvidia driver specific options, only parsed if Driver=nvidia
[driver-nvidia]
# Module name to load, defaults to Driver if empty or unset
KernelDriver=nvidia
PMMethod=auto
# colon-separated path to the nvidia libraries
LibraryPath=/usr/lib/nvidia:/usr/lib32/nvidia
# comma-separated path of the directory containing nvidia_drv.so and the
# default Xorg modules path
XorgModulePath=/usr/lib/nvidia/xorg/,/usr/lib/xorg/modules
XorgConfFile=/etc/bumblebee/xorg.conf.nvidia
## Section with nouveau driver specific options, only parsed if Driver=nouveau
[driver-nouveau]
KernelDriver=nouveau
PMMethod=auto
XorgConfFile=/etc/bumblebee/xorg.conf.nouveau -
W530 Boot Failure with out any BSOD
I bought my thinkpad w530 in Oct. 2012. It works perfect until recent month.
At the beginning, it can't wake up in the sleep mode. If I connect the AC power, it reset the BIOS time.
And nowadays, when i power off this laptop, it can't boot. And I remove and setup the battery, It restored. But if I first connect the ac power/dock, and remove-setup the battery, the BIOS time is reseted.
I updated all my drivers. The failure is still here. I wonder if oneday it died forever?
Thinkpad W530 2lu, 32G DDR 3 Kinston, 500G HDD. K2000mCan you try resetting your BIOS settings to defaults?
It's also possible that your CMOS battery is depleted, in which case you would have to replace it.
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 -
ThinkPad W530 with the Quadro K1000M or K2000M? BTSBEST coupon expires tomorrow!
I've been looking for a good 15" Ivy Bridge laptop that will last four or five years without breaking or becoming totally obsolete. The ThinkPad W530 fits these criteria. I'll be using it for playing Portal 2 and Minecraft, watching (and sometimes encoding) 1080p video, developing graphical and other programs (fractal renderers, procedural generation, etc), and web design. Programs I run include Eclipse, VMware, x264, Photoshop, and Firefox (with pretty many extensions, userscripts, and tabs).
I'm getting the Intel Core i7-3610QM, 1600x900 display (for 1080p I'd use an external monitor larger than 15"), 4GB RAM and 320GB hard drive (I can upgrade them myself more cheaply), and Intel Centrino Advanced-N 6205 AGN. So: which graphics card should I get, the K1000M or K2000M? The K1000M has 192 pipelines at 850MHz; the K2000M has 384 at 745MHz. Is having twice as many shaders worth an extra $250 for my purposes? Four years from now, will the K2000M be acceptable while the K1000M is obsolete? And if I do get the cheaper K1000M, should I upgrade to the Core i7-3520M for $50 or the i7-3720QM for $85? (Why does the dual-core 3520M cost more than the quad-core 3610QM?)
The BTSBEST coupon is saving me $300 on this configuration, but it expires tomorrow, so I need to make a decision. Thanks for any advice!
ThinkPad W530 (Intel Core i7-3610QM, NVIDIA Quadro K2000M, 4GB DDR3, 320GB 7200RPM, 15.6" 1600x900, Intel Centrino Ultimate-N 6300)Hello Rangi42,
Personally I would go with the K2000M. I am a big gamer and that graphics card would be great for Minecraft and Portal 2. Graphics should run smoothly. I would agree on the RAM and hard drive upgrade, maybe an SSD to make the computer run faster and smoother.
I am not sure why the price of the 3520M is cheaper than the 3610QM.
The w530 in general is a great computer for graphics development like your web design. Video editing is good on the W530 as well.
Hope this helps,
Alex
Was this or another post on the forum helpful? Click the star on the left side of the screen to give kudos! Did someone solve the problem you encountered? Click Solution Provided to let us know!
What we Do in Life will Echo through Eternity. -Maximus Aurelius -
Thinkpad W530 wont boot or charge
Hi, I have had my Thinkpad W530 for almost 2 years now. It has worked fine in the past. I went to turn it on yesterday (I havent used it in a few weeks as it is summer) and it turned on but when it got to the THINKPAD screen (the one with the "to interupt normal startup press enter") it shut right off... I tried turning it on several more times and it did the same thing until it did not even respond. The light around the power button didnt even blink. I thought it was dead so i plugged it in and that also didnt help. The charging light will not even light up. I looked at other forums but i couldnt find the same problem.I tried taking the battery out and unplugging, holding the power button for 1 minute and plugging back in and it did not help. It will not run with any combination of power source (just battery, battery and outlet, just outlet)
Try the unplugging thing you did with the CMOS (backup) battery disconnected.
-
ThinkPad W530 with Windows 7 x64 Pro BSOD when connecting to projector
Hi,
I have 2 identical ThinkPad W530 laptops model 244723G
Both are set to discrete graphics from BIOS because with optimus driver my projector will not work at all.
But how i have other issue that causes BlueScreen when connection laptop to projector.
I have installed latest driver from Lenovo download site -> still BSOB when connecting to projector.
When i install driver from Nvidia site it fixes BSOD issue with discrete graphics and external projector.
Can same one else confirm that there is a error on Lenovo optiomus driver when using discrete graphics?
Solved!
Go to Solution.Would you mind posting the links to those drivers, or copying their exact name for us to search on the appropriate site(s)?
I use a w520 (quad core/nVidia 1000 discrete graphics board) with a projector and anything that makes that smoother I have to consider. There have been posts about how to re-create the usual ThinkPad use of the F7 key for choosing projector view mode but I admit I have never been able to take the time (and risk of failure) to try the swap of internal files to make it happen. (Starting a project like that always makes me feel I have to have time to do the project and if it goes wrong re-install the OS and all updates -- all before the next time the laptop is needed for anything important. That condition is almost never possible.)
Yeah, I know, I'm chicken! <grin>
jonathan7007
4276-37U -- W520. Still have an X61t. First laptop in my house was an Osborne! Now that was a cool computer. (...for its time!) -
ThinkPad W530 with Windows 8 x64 Pro BSOD when connecting to projector
Nine, that only covers Widows 7. Many people in this thread have reported the problem using Windows 8. Has that been addressed by Lenovo yet? Stability problems like this should NEVER be allowed to go so long without a resolution.
Edit Note : This thread was created base from the previous thread "ThinkPad W530 with Windows 7 x64 Pro BSOD when connecting to projector. As we currently Cx reporting facing the same issue on Win8 I have seperated this thread in order not toconfuse other customer. For cutomers facing this issue please continue posting in this thread.Hi shan_mcarthur,
Thanks for posting. I read through this thread again and noticed that most of customers here do indeed have Windows 7 installed as what the title represented unless I'm mistaken or may have missed out are you or anyone else here facing the same issue on Windows 8. If that is the case I'll be more than happy to bring this up with the teams but it will have to be a new thread though as I'd like to keep the resolution separate based on the OS use just to not confuse other customer .
For those facing the same issue above on Win8, please do let me know so we can start a discussion around this.
Do let me know.
Regards -
New Thinkpad W530 order direct from Lenovo with integrated mobile will not connect to broadband
I purchased a W530 with integrated mobile and have been trying to connect with various networks to no avail. I have a Type 2436-CTO S/N xxxxxxx 13/08 and Windows 8 came installed when I received. I have upgraded BIOS and everything that Lenovo solutions says I need to update.
The MEID is A1xxxxxxxxxxx. It came with an integrated Sierra Wireless MC8355-Gobi 3000 modem. I have downloaded an updated driver for Windows 8 for the MC8355. I have spoken with almost every Lenovo technical person as well as taken the computer to various network stores and so far no one can figure out why it won't connect to Verizon.
Verizon says I'm active and the computer error message says I am not active. Every tech has tried to look at the system by logging into my computer and no one can figure it out. The device manager says the MC8355 is working. Interesting when it was shipped to me it also had an AT&T sim card installed. After I had signed up with AT&T and one mo of paying for service they determined it would not work on their network. Finally someone told me to take the AT&T sim card out and it still will not connect.
Verizon tells me I do not need a sim card as I have the MC8355 but they can't tell me why I can't connect. Now I've paid for Verizon service for one month and still cannot connect. Everything else works fine with the W530. I've owned ThinkPads exclusively since the first one ever came out. I've never not been able to connect to mobile broadband with any others. I also went through about two weeks of trying to connect with Lenovo Mobile Access and that did not work because I'm running Windows 8. Finally a nice gentleman called me from LMA to tell me it will not work after all the time of connecting and being on the road. I could go back to an old ThinkPad to travel with but I'm determined to get my new one to connect. Any more advice or anything anyone can tell me try?
Moderator Note; imei & s/n edited for member's own protection
Solved!
Go to Solution.Hi swade01,
Have a look there: http://support.lenovo.com/en_US/detail.page?DocID=HT077670
It might help you hopefully.
Vince.
Knowledge is of two kinds. We know a subject ourselves, or we know where we can find information on it.
ThinkPad T510 4313-CTO Windows 8 x64 - Intel Core i7-620M - NVIDIA NVS 3100M - 8GB RAM - 240GB SSD- Intel Centrino Ultimate-N 6300 - Gobi 2000.
ThinkPad Helix 3697-CTO Windows 8.1 x64 - Intel Core i7-3667U - Intel HD Graphics 4000 - 8GB RAM- 256GB SSD - Intel Centrino Advanced-N 6205 - Ericsson C5621gw -
Is cs5 compatible with Lenovo ThinkPad W530?
Quick question... I own a copy of the CS5 and am thinking of buying the
Lenovo ThinkPad W530 2438-4CU 15.6" .... It appears to be a good match.. Any thoughts?
JamnjulesThat looks like a great machine. Yes it should be fine with CS5 as CS5 is compatible with Win 7 Pro.
-
Sudden shut down: ThinkPad W530 + Anker USB 3.0 Dock with DisplayLink driver
Hi all,
I have a W530. There, I use Anker USB 3.0 Dual Display Universal Docking Station driven by DiplayLink which is connected one 23" LCD, NEC MultiSync P232W. My W530 works well when it starts up alone without the USB docking station. But, when I start up it with the docking station connected USB 3.0 port, my W530 encounters sudden shutdown. Especially, it often happens during starting up Windows OS or in 5 minutes from starting up. Once, succeeded starting up and passed first 5 minutes, it works well until it is shut down or falls into sleep mode.
To fix it, I reinsatalled Windows 8.1 and updated related drivers. But the problem has not fixed. I am doubtful of hardware problems but I am not sure which one has problems.
Any ideas what might cause this annoying problem?
I listed my models and drivers.
Hardware
ThinkPad W530, Product: 243852U, BIOS: G5ET98WW (2.58)
Anker Anker USB 3.0 Dual DisplayDocking Station (connected with two external HDD, intuos pen tablet, USB keyboard and LAN cable)
NEC MultiSync P232W (connected with the Dock via DVI cable)
Driver
Windows 8.1
DisplayLink 7.6.56275
Solved!
Go to Solution.The problem probably has been fixed.
I received an advice from Anker customer support.
I followed the steps below.
1.Find Device manager
2.Look for Universal Serial Bus Controllers---USB Root Hub right click USB Root Hub then select properties,
3.On the tabs above find Power Management--- uncheck the box "Allow the computer to turn off this device to save power" and then click “ok”. Reboot the laptop/computer.
After changing the setting, I have not met the problem so far.
TN -
Lenovo Thinkpad T520 doesn't boot with GPT slices on FreeBSD 9-BETA3 - BIOS bug?
Hi!
I've bought a brand new Lenovo Thinkpad T520 laptop and decided to install FreeBSD 9 Beta 3 following this guide.
But when I rebooted the system, it simply doesn't boot (turns out to the BIOS boot menu).
It's even doesn't boot with default FreeBSD 9 UFS-on-GPT installation scheme through bsdInstaller
Changing BIOS (latest, 1.31) settings BIOS Startup->UEFI/Legacy Boot from "Both" to "Legacy only" has no effect. As FreeBSD AFAIK doesn't support UEFI boot, legacy boot should work picking up and starting pmbr (protected MBR record), but it doesn't.
However, FreeBSD 9 UFS-on-MBR installation (with mbr boot record and FreeBSD slice in MBR partition instead of GPT) works fine.
It seems to me that UEFI/Legacy Boot "Legacy" setting actually has no effect if 0xEE type Primary partition entry is present on disk.
First of all, has anyone installed Linux or FreeBSD with GPT partitioning scheme on latest Thinkpads?
And the second one, as I've saw similar problem on FreeBSD forum thread about T420s laptop I believe that this may be a bug in the BIOS. How can I fill the bugreport or send an e-mail to support or developers, as, obvious, phone support can consult only about Windows OS.Volker1 wrote:
I've got a suspicion that the Thinkpad bios/efi is not simply executing the first stage bootloader, but looking around on the GPT disk and then crapping its pants when it doesn't find Windows.
Right now I have a MBR-formatted harddisk in the ultrabay with the bootloader in the MBR. Once I get the bootloader off the MBR disk, I can easily continue to boot from my GPT-formatted SSD.
Yes, it seems that it's a BIOS bug at least on T520, T420s and W520 laptops. Even in "Legacy" mode first stage bootloader doesn't execute if partition type is 0xEE (GPT).
Hope Lenovo developers will fix it. They fixed something on BIOS 1.31
[Problem fixes]
- Fixed an issue where the computer might not be booted from bootloader program.
but it doesn't work for now. Pity. -
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 -
Arch does not show up in Grub when dual booting with windows 8
I just installed Arch linux, dual booting with windows 8 using the beginners guide[https://wiki.archlinux.org/index.php/Beginners'_Guide] itself. Now Grub is installed and i can only find Windows 8 and I cannot find Arch. Is there a way I can find if arch linux has been installed and show up in Grub.
Sorry, I am a newbie, but i chose to post this topic here and not newbie corner as it is installation related.
My windows 8 is installed on /dev/sda1 with ntfs partition type. Arch Linux is installed on /dev/sda6 and it is ext4 partition. I dont know if this info helps. I am using Thinkpad R61
Last edited by sutro_droid (2013-03-06 00:30:48)ivokosir wrote:It may be that you didn't install os-prober before running grub-mkconfig. This happened to me once, I hope I'm not too late to warn you.
I am sorry, yes you are too late. I have wiped windows 8 and performed clean install. No regrets. And as a matter of fact, I did grub-config and then installed os-prober. That could be the problem. Thanks. I will try this again another time. -
Premiere CC crashes on launch on Lenovo ThinkPad W530/Quadro K2000M
Hey everyone!
I can't get Premiere Pro CC to launch on my new laptop--Lenovo ThinkPad W530 with Quadro K2000M graphics. On launch I get "Adobe Premiere CC has stopped working."
The K2000M is on the approved list, so I was hoping that wouldn't be a problem. But uninstalling the nVidia drivers does actually allow me to open Premiere, so clearly that is the problem. I went to the Lenovo site and I'm using the most up-to-date driver (9.18.13.1270/8.15.10.2725/G5DE43WW).
Things that didn't work that I've seen elsewhere on this forum:
- signing out of and into Creative Cloud
- running Premiere in Windows 7 compatibility mode
- running Premiere as administrator
Any help in getting the program and the nVidia running at the same time would be appreciated...I have a project coming up shortly.
Matt Levie
If it helps, here's the problem signature:
Problem signature:
Problem Event Name: BEX64
Application Name: Adobe Premiere Pro.exe
Application Version: 7.2.1.4
Application Timestamp: 52aed7f3
Fault Module Name: StackHash_1dc2
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 0000000000000000
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 1dc2
Additional Information 2: 1dc22fb1de37d348f27e54dbb5278e7d
Additional Information 3: eae3
Additional Information 4: eae36a4b5ffb27c9d33117f4125a75c2Unfortunately, the crash data you posted doesn't give us any clues.
It looks like the driver you're on is very fresh: 2014-1/5. Another user recently reported a different problem on a Lenovo w/ the K1000M (http://forums.adobe.com/message/5987620#5987620). Don't know yet what driver he's on, but if he's also on a new one, I'd begin to suspect a bug in the driver.
Some additional data could be illuminating. Premiere installs a utility called GPUsniffer. You'll find it here: C:\Program Files\Adobe\Adobe Premiere Pro CC. However, unless you read quicker than I do--and I mean waaaay faster--launching it from there won't do much good. You'll have to open the command console, navigate to the path above, and type gpusniffer.exe. (Let me know if you need more explicit instructions for getting around in the console.) Then copy the report and paste it here.
edited to add: To help determine if the current Lenovo K2000M driver is at fault--and possibly get yourself back in business--please roll back to an earlier driver.
Maybe you are looking for
-
HT4356 How do I set up iPad to use wireless Kodak printer?
I have iPad 2. looked at air print instructions but Kodak printers are not listed. can I not use iPad with printer that is not listed?
-
Escape does not work.
-
How to import XMP metadata in pdf
Could you please explain me, how to import XMP metadata in pdf file through "Live Cycle ES"?
-
HT4972 How can I update my iphone 3G iOS 4.0 to iOS 5.0.1
Hi! I am sure you can help me! I have an Iphone 3G with iOS 4.0.0 not factory unlocked and i want to know how to upgrade it to iOS 5.0.1,and i am a beginner in this things,Please someone help me!
-
How can i invoke EJBs in a different JVM