05-28-2014 01:29 AM - edited 05-28-2014 02:16 AM
I am not near my Y510p at the moment but later today I will get back to that machine and see if I have any specific configs that I can share with you - certainly I have been booting my Y510p for some time without problems and arch linux runs nicely, but I can't remember off the top of my head if I did anything special to avoid the blank screen issue. Clearly you have arch linux booting OK but there will be some small change to the configs for boot to get your screen working normally.
One thing I am remembering but without the benefit of my Y510p running where I am right now is the question of what is in your /etc/mkinicpio.conf - do you have a modules line:
If not then you could add that in by editing the existing line starting MODULES, and then regenerate the initiramfs - by doing as root:
mkinitcpio -p linux
and then reboot.
I will check the contents of my mkinitcpio.conf later and also check what I did, if anything, about blacklisting modules. In the meantime try adding in the i915 module to the initramfs as above and it may get you going.
What method are you using to start X are you logging in to a text console and typng startx or are you using systemd to start it?
What I do for getting kde login greeter and X started is to
systemctl start kdm
and when I am sure it works soon after the install then
systemctl enable kdm
so that it will start automatically at boot. If it is running the graphical.target i.e. X is running then if you were on VT1 logged in on a console it should switch to VT7 for the graphical console.
Also systemctl start graphical.target should get you to a graphical screen. and to make that happen at boot also then systemctl enable graphical.target.
Also check the arch wiki at https://wiki.archlinux.org/index.php/Intel
05-28-2014 03:48 PM
Thanks again for the response mcloaked.
I have attempted the solution involving the i915 module and that does not work. I run into the same problem. If I do not provide the 'nomodeset' parameter the display freezes up and I have no clue what is going on. If I do provide it, then I arrive at the login prompt, but when attempting to launch the X server using:
It fails miserably because KMS is required by X Server to run.
To answer your question, I start, or attempt to start X, using the terminal (TTY1).
What I don't understand is how you got past the 'nomodeset' issue? From the very beginning I had to provide this parameter when booting in order to have a usable machine. As I understand it, before you set KDM to start automatically at boot, you test it by doing:
$ systemctl start kdm
I assume that this works for you, but I'm confused as to how you were able to even invoke that command. I haven't been able to get a responsive terminal without 'nomodeset' and according to Arch Wiki's Intel entry: "Kernel Mode Setting (KMS) is required in order to run X and a Desktop environment. " Did you ever have to use this parameter in your build? If so, how did you get rid of it?
05-29-2014 02:38 AM - edited 05-29-2014 03:25 AM
In order to understand what your system is doing it will be necessary to provide a certain amount of detailed information about your hardware as well as the output of a number of commands. Since I have not seen the detailed set of steps that you took to get the various packages installed I will ask for some information to compare with my system.
I did check and I don't have i925 in the mkinitcpio.conf MODULES line in this machine but I did need it in a different one so I was wrong about that though I was working from memory at the time.
Firstly let's check that you have the same graphics hardware as me - what is the output of the command which on my system is:
$ lspci | egrep VGA
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 750M] (rev a1)
If your graphics chips are different then a different approach may be needed for your system.
Secondly what xorg packages do you have installed? Compare with mine:
# pacman -Qs xorg | grep local/xorg
local/xorg-bdftopcf 1.0.4-1 (xorg xorg-apps)
local/xorg-docs 1.7-1 (xorg)
local/xorg-font-util 1.3.0-1 (xorg-fonts xorg)
local/xorg-fonts-100dpi 1.0.1-4 (xorg)
local/xorg-fonts-75dpi 1.0.3-1 (xorg)
local/xorg-fonts-encodings 1.0.4-3 (xorg-fonts xorg)
local/xorg-iceauth 1.0.6-1 (xorg-apps xorg)
local/xorg-luit 1.1.1-2 (xorg xorg-apps)
local/xorg-mkfontdir 1.0.7-1 (xorg xorg-apps)
local/xorg-mkfontscale 1.1.1-1 (xorg-apps xorg)
local/xorg-server 1.15.1-1 (xorg)
local/xorg-sessreg 1.0.8-1 (xorg-apps xorg)
local/xorg-setxkbmap 1.3.0-1 (xorg-apps xorg)
local/xorg-smproxy 1.0.5-1 (xorg-apps xorg)
local/xorg-x11perf 1.5.4-1 (xorg-apps xorg)
local/xorg-xauth 1.0.9-1 (xorg-apps xorg)
local/xorg-xbacklight 1.2.1-1 (xorg-apps xorg)
local/xorg-xcmsdb 1.0.4-1 (xorg-apps xorg)
local/xorg-xcursorgen 1.0.5-2 (xorg-apps xorg)
local/xorg-xdpyinfo 1.3.1-1 (xorg-apps xorg)
local/xorg-xdriinfo 1.0.4-3 (xorg-apps xorg)
local/xorg-xev 1.2.1-1 (xorg-apps xorg)
local/xorg-xgamma 1.0.5-1 (xorg-apps xorg)
local/xorg-xhost 1.0.6-1 (xorg-apps xorg)
local/xorg-xinput 1.6.1-1 (xorg-apps xorg)
local/xorg-xkbcomp 1.2.4-1 (xorg-apps xorg)
local/xorg-xkbevd 1.1.3-1 (xorg-apps xorg)
local/xorg-xkbutils 1.0.4-1 (xorg-apps xorg)
local/xorg-xkill 1.0.4-1 (xorg-apps xorg)
local/xorg-xlsatoms 1.1.1-1 (xorg-apps xorg)
local/xorg-xlsclients 1.1.3-1 (xorg-apps xorg)
local/xorg-xmodmap 1.0.8-1 (xorg-apps xorg)
local/xorg-xpr 1.0.4-1 (xorg-apps xorg)
local/xorg-xprop 1.2.2-1 (xorg-apps xorg)
local/xorg-xrandr 1.4.2-1 (xorg-apps xorg)
local/xorg-xrdb 1.1.0-1 (xorg-apps xorg)
local/xorg-xrefresh 1.0.5-1 (xorg-apps xorg)
local/xorg-xset 1.2.3-1 (xorg-apps xorg)
local/xorg-xsetroot 1.1.1-1 (xorg-apps xorg)
local/xorg-xvinfo 1.1.2-1 (xorg-apps xorg)
local/xorg-xwd 1.0.6-1 (xorg-apps xorg)
local/xorg-xwininfo 1.1.3-1 (xorg-apps xorg)
local/xorg-xwud 1.0.4-1 (xorg-apps xorg)
Next let's check what Intel and nouveau drivers you have - mine are:
# pacman -Qs Intel| grep local
local/xf86-video-intel 2.99.911-2 (xorg-drivers xorg)
# pacman -Qs nouveau| grep local
local/xf86-video-nouveau 1.0.10-2 (xorg-drivers xorg)
What mesa packages do you have installed? Mine are:
# pacman -Qs mesa| grep local
You should also have xf86-video-nouveau and xf86-video-intel as well as libva-intel-driver installed. I also have svga-dri installed.
If you are missing any of these then install them with pacman -S package-name or if you want to you can use the --needed flag so that it will only install if the package or dependencies are not already installed i.e. pacman --needed -S package-name
I boot using rEFInd and the refind_linux.conf file contains the kernel boot lines which have no reference to mode setting at all:
"Boot with defaults" "root=PARTUUID=850c708f-e49d-4644-b2a5-2e7f2e4f179a rw"
"Boot to console" "root=PARTUUID=850c708f-e49d-4644-b2a5-2e7f2e4f179a rw rootfstype=ext4 systemd.unit=multi-user.target"
"Boot Fallback to console" "root=PARTUUID=850c708f-e49d-4644-b2a5-2e7f2e4f179a rw initrd=/boot/initramfs-linux-fallback.img rootfstype=ext4 systemd.unit=multi-user.target"
My /etc/X11 has
# ls /etc/X11/
twm xinit xorg.conf.d
so there is no xorg.conf and you should check that yours is the same.
I have no files in /etc/modprobe.d/
Let's see if your system has everything that I list above, and once your system has the same package set if it still does not give you a graphical screen at boot we can make more comparisons.
05-29-2014 02:47 AM - edited 05-29-2014 02:57 AM
Concerning modesetting there is a comment in https://wiki.archlinux.org/index.php/kernel_mode_setting
Late KMS start
Intel, Nouveau and ATI drivers already enable KMS automatically for all chipsets, so you need not install it manually.
The proprietary NVIDIA and AMD Catalyst drivers do not use the open driver stack. In order to use KMS you should replace them with open source drivers."
I trust that you did not have anything left over from when you had the proprietary Nvidia driver as that could mess things up for graphics. Also the proprietary driver is actually available in the arch repos and there are wiki entries for it.
You should not have any Nvidia packages installed - check the list below - if you have Nvidia packages then you will need to remove them (Pacman -R ...)
# pacman -Ss nvidia-
NVIDIA drivers for linux, 304xx legacy branch
NVIDIA drivers libraries symlinks, 304xx legacy branch
NVIDIA drivers for linux-lts, 304xx legacy branch
NVIDIA drivers utilities and libraries, 304xx legacy branch
NVIDIA drivers libraries symlinks
NVIDIA drivers for linux-lts
NVIDIA drivers utilities
OpenCL implemention for NVIDIA, 304xx legacy branch
NVIDIA Optimus support for Linux through VirtualGL
NVIDIA Cg libraries
So it should not even be necessary to refer to the drivers from the Nvidia web site.
06-10-2014 02:40 PM
I want to ask if some one here gets working nvidia sli with bumblebee. I am thinking about buying this notebook. I had Lenovo Y580, so I basically know how to setup laptop with optimus on linux, but I don't know if I should buy it with second gpu. I know that without second graphic it would be simply the same as my old notebook. I don't wanna buy second gpu that I couldn't use at all (I am using only linux for most of the time). My idea is that if nvidia driver supports it and bumblebee is only loading nvidia driver and starting it in separate xserver, it should work. But I can't be sure. So do you know if it is working? Just use intel gpu and nvidia sli graphics with bumblebee.
07-03-2014 11:24 AM - last edited on 07-03-2014 11:39 AM by andyP
Here is the most recent information regarding the Lenovo IdeaPad Y510P notebook PC and GNU/Linux with regard to getting nVidia SLi to work on GNU/Linux platforms. It seems that a VBIOS VGA may be required for the second nVidia Geforce GT 755M 2 GB VRAM GPU. It also seems that nVidia graphics driver 340.17 Beta for GNU/Linux offers nVidia SLi and Mutli-GPU Frame Rendering support.
The nVidia GNU/Linux team is smaller compared to the Microsoft Windows support team. You can only reach them on the nVidia Developer Zone under the GNU/Linux sub-forum. It will take some time for them to reply to your information and comments. However, it does look like nVidia is working on this issue by trying to reproduce it on a Lenovo IdeaPad Y510P notebook PC using GNU/Linux to enable nVidia SLi technology for the dual nVidia Geforce GT 750M or 755M GPUs. Be patient as we are getting closer to the solution.
I would like for more people within this Lenovo community to respond. It looks like we're going to have to do some back and forth between this and the nVidia support forums to solve this problem.
Feel free to contact me at xxxxxxxxxx. Please specify in the subject line that it has to do with the Y510P and GNU/Linux.
For the record, I got Ubuntu 14.04 LTS 64 bit GNU/Linux to install properly on my Lenovo IdeaPad Y510P by using the Legacy Mode and Legacy First BIOS boot mode. I also installed the nVidia Geforce 331.38 graphics drivers, but SLi does not work yet. I'm wary of trying out the 340.17 Beta graphics drivers until they stabilize in the future. So, I'm taking a wait and see approach.
Moderator note; e-mail address removed to stop the spambots getting it
03-11-2015 02:30 AM