GoogleCodeExporter
commented
9 years ago [deleted comment]Open GoogleCodeExporter opened 9 years ago
GoogleCodeExporter
commented
9 years ago [deleted comment]Reported to nvidia Linux support forum:
http://www.nvnews.net/vbulletin/showthread.php?t=149043Original comment by tilman.vogel on 17 Mar 2010 at 9:35
GoogleCodeExporter
commented
9 years ago I've been testing multi displays now too. Unfortunately it seems the
ConnectedMonitor
option overrides detection for ALL ports, and EDID probing does not work
reliably (or
at all for the internal screen, which only has info in ACPI).
I set ConnectedMonitor to "DFP-0, DFP-1, CRT-0" for internal, HDMI and VGA
respectively. nvidia's driver then shows all monitors in nvidia-settings, so
they can
be enabled, but it does not reliably detect available modes, not even when
"Detect
Displays" is clicked. Typically, monitors that were connected when X starts
work, and
*sometimes*, another screen can be added.
The problem should be possible to reduce somewhat by storing EDIDs so the proper
modes can be selected, but this doesn't solve everything (for instance, varying
aspect ratios).
For your particular ACER monitor, AFAICT it only has a VGA cable, which means
you
need CRT-0, not DFP-1.Original comment by yann.ver...@gmail.com on 18 Apr 2010 at 1:39
GoogleCodeExporter
commented
9 years ago You are right: that ACER monitor only has capability for VGA cable.
I may already have tried that in the past, but I'm not sure of it though.
I will try it again next week, based on your tip, and I'll post the results
afterwards.Original comment by stephv...@gmail.com on 20 Apr 2010 at 10:30
GoogleCodeExporter
commented
9 years ago In my case, specifying "DFP-0, CRT-0" in the "ConnectedMonitor" option enables
me to
connect an external monitor and have VAIO sends its output.
However, as soon as I do that, the main LCD panel completely loses the
backlight (even
though I can still see that it's displaying images), making the LCD panel
effectively
useless. The same happens when I resume from a suspend or switch to a console
and come
back to X, so it's possibly related to issue #3,Original comment by kohsuke....@gmail.com on 29 Apr 2010 at 6:46
GoogleCodeExporter
commented
9 years ago [deleted comment]I did make it to connect two monitors to my Kubuntu 10.04. VPCF11Z1E
here is my xorg.conf
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (buildd@yellow) Fri Apr 9 11:51:21 UTC 2010
Section "ServerLayout"
# Removed Option "Xinerama" "0"
# Removed Option "Xinerama" "1"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor0"
VendorName "Unknown"
ModelName "LG L204WT"
HorizSync 28.0 - 83.0
VertRefresh 56.0 - 75.0
Option "DPMS"
EndSection
Section "Monitor"
# HorizSync source: unknown, VertRefresh source: unknown
Identifier "Monitor1"
VendorName "Unknown"
ModelName "LG L204WT"
HorizSync 28.0 - 83.0
VertRefresh 56.0 - 75.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GT 330M"
EndSection
Section "Device"
Identifier "Device1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GT 330M"
BusID "PCI:1:0:0"
Screen 1
EndSection
Section "Screen"
# Removed Option "metamodes" "DFP-0: nvidia-auto-select +0+0"
# Removed Option "TwinView" "0"
# Removed Option "metamodes" "DFP: nvidia-auto-select +0+0"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "ConnectedMonitor" "DFP-0,CRT"
Option "CustomEDID" "DFP-0:/etc/X11/sonyedid1.raw"
Option "TwinView" "1"
Option "TwinViewXineramaInfoOrder" "DFP-0"
Option "metamodes" "CRT: 1680x1050 +1920+0, DFP: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Device1"
Monitor "Monitor1"
DefaultDepth 24
Option "ConnectedMonitor" "DFP-0,,CRT"
Option "TwinView" "0"
Option "TwinViewXineramaInfoOrder" "CRT-0"
Option "metamodes" "CRT: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
-
First i did add CRT to my ConnectMonitor rebooted X to get the full xorg file
config,
then i took my EDID file and copyd it from windows 7 to kubuntu. /etc/X11/
I will attach EDID for VPCF11Z1E monitor
Hope this helps.Original comment by partygam...@gmail.com on 14 May 2010 at 1:14
Attachments:
GoogleCodeExporter
commented
9 years ago I'll see if I can test it with your set-up soon. Some questions, though:
- Have you tried without specifying the graphics card twice?
- Is your additional monitor positioned on the left or the right of your vaio?
- What's the resolution of your secondary monitor?Original comment by mpkos...@gmail.com on 18 May 2010 at 3:08
GoogleCodeExporter
commented
9 years ago this solution works for me. Using this xorg.conf and edid the monitor (connected
through VGA) was detected. Afterwards I was able to configure everything via
nvidia-settings. The card is a geforce 310M (my pc is a VAIO VPCS11E7E)Original comment by mar.ro...@gmail.com on 19 May 2010 at 12:18
GoogleCodeExporter
commented
9 years ago partyga...@hotmail.co.uk's xorg.conf also works for me - VPCF11M1E. Thanks a
lot!Original comment by kalu...@gmail.com on 1 Jul 2010 at 9:37
GoogleCodeExporter
commented
9 years ago Better yet, I just installed with NVIDIA-Linux-x86_64-256.44.run and EVERYTHING
works out of the box: Dual mooitor (twinview), duplicated view, etc. I used
nvidia-settings to change to twinview, to have separate monitors, everything. I
had it destroy the xorg.conf on install. Finally this machine is arriving. Original comment by ra...@randyfay.com on 16 Aug 2010 at 7:27
GoogleCodeExporter
commented
9 years ago How about HDMI? Anyone found a way to enable this port? andyfay123, does it
work with new drivers?Original comment by kalu...@gmail.com on 16 Aug 2010 at 7:37
GoogleCodeExporter
commented
9 years ago And yes, NVIDIA-Linux-x86_64-256.44.run worked with HDMI as well. I'm amazed.Original comment by ra...@randyfay.com on 16 Aug 2010 at 8:33
GoogleCodeExporter
commented
9 years ago Thanks for the update! It also works for me too!Original comment by kalu...@gmail.com on 16 Aug 2010 at 9:43
GoogleCodeExporter
commented
9 years ago YES !! Finally this is working with NVIDIA-Linux-x86_64-256.44.run.
I think this issue can now be closed.Original comment by stephv...@gmail.com on 18 Aug 2010 at 12:01
GoogleCodeExporter
commented
9 years ago Latest nvidia driver also works for me.
I vote to close this bug.Original comment by nuno.mt....@gmail.com on 8 Sep 2010 at 1:46
GoogleCodeExporter
commented
9 years ago before closing, anyone can confirm it does work with the very latest 256.53
driver?Original comment by stephv...@gmail.com on 8 Sep 2010 at 2:20
GoogleCodeExporter
commented
9 years ago Sorry, Iwhen I said the latest I meant 256.53.
I'm using nvidia-drivers 256.53 on Gentoo and I can connect another screen on
the fly.
I also don't need the EDID workaround in the wiki to get the laptop display
working.Original comment by nuno.mt....@gmail.com on 8 Sep 2010 at 3:14
GoogleCodeExporter
commented
9 years ago Confirmed, works with the latest nvidia-driver 256.53 on Debian testing with
VPCF12C5EOriginal comment by glaubens...@gmail.com on 8 Sep 2010 at 5:03
GoogleCodeExporter
commented
9 years ago Thanks for all the great job done.
It was OK for me with a vaio VPCF11S1E and drivers x86_64-256.44
Upgrade was fine during august with drivers from ppa:ubuntu-x-swat/x-updates
HOWEVER, xorg failed this monday 13 september 2010 because of the automatic
upgrade of nvidia drivers to 260.19.04 version
FORTUNATELY, it was possible to reinstall driver 256.53 using procedure
described here :
http://www.ubuntugeek.com/howto-install-nvidia-drivers-manually-on-ubuntu-10-04-
lucid-lynx.html
So, be careful before the use of nvidia-driver 260.19 !!!Original comment by didier.v...@gmail.com on 13 Sep 2010 at 8:34
GoogleCodeExporter
commented
9 years ago Guys. Wouldn't be possible to enable Fn-F7 combination for switching between
1st-2nd-double monitors?Original comment by oleksiy....@gmail.com on 2 Oct 2010 at 7:03
GoogleCodeExporter
commented
9 years ago 2010 November 26th : after an automatic Ubuntu update which broke again
graphics, i made a new trial with NVIDIA-Linux-x86_64-260.19.21.run. It didn't
work !
I came back to NVIDIA-Linux-x86_64-260.53.runOriginal comment by didier.v...@gmail.com on 29 Nov 2010 at 10:06
GoogleCodeExporter
commented
9 years ago Using version 260.19.29 of the Nvidia drivers and the xorg.conf file in comment
7 (but without the EDID file - in fact, it seems that with driver 260.19.29 the
EDID issue no longer exists), I was able to get the VGA port to work.
I have still not found a way to get the HDMI port to work, but baby steps,
right?Original comment by lengau on 30 Dec 2010 at 12:19
GoogleCodeExporter
commented
9 years ago I have a Vaio F13Z and my HDMI is working. I use an application called "disper"
( http://willem.engen.nl/projects/disper/ ) that, once you insert the cable,
you can run the command "disper -l" to check the available outputs.
Once you've set the displays in the xorg.conf file, you inly need to do "disper
-S" to send the HDMI output to the TV and "disper -s" to the laptop screen
again. A reminder that when I take the cable out, my screen will not fall back
to the laptop screen, you have to manually shoot the "disper -s" command. I
want to write a script so I can associate this to the Menu (window) key plus
the F7 key so I can switch between primary and secondary screen without having
to shoot the command (if someone wants to do that before I do, be my guest and
don't forget to share!)
Then, I changed my "/etc/X11/xorg.conf" to add the extra display and also to
change the names of the outputs, according to the "disper -l" command (you can
read the display codes right after the "display" keyword). In the middle of
this, I think I had the NVidia Xserver Settings graphical application open too,
so I could check if the names where correct and to try and detect my Flat
Screen TV HDMI connection.
Also, note the "metamodes" in the "Screen" section. These ones are used so I
can switch between each one of those, they correspond to "TV Display Only",
"Laptop Display Only" and "Clone Displays" mode, respectively. You can easily
add a forth metamode by changing the "+0+0" to the one Display that you want to
be your primary screen and the other one your secondary, and the "+0+0" is the
resolution where you want to start the second screen. So if you want the
secondary screen to be your TV, you can add a metamode like this: "DFP-1:
nvidia-auto-select +1980+0, DFP-0: nvidia-auto-select +0+0" (separate it with a
';' character from the other metamodes)
I leave my xorg.conf in attachment. If you have any doubts and I can help you,
I'll do it ;)
The only 2 issues I have now is to find a method to switch the monitor output
to the HDMI once I insert the cable and the other is how to make pulseaudio
sound server to force all aplications to send there audio output to the HDMI
when it actually detects that I've changed to my HDMI, I didn't find a method
to that yet.Original comment by sigmadra...@gmail.com on 30 Dec 2010 at 1:42
Attachments:
GoogleCodeExporter
commented
9 years ago Thank you, sigmadraconis!
I used the xorg.conf file you provided and was able to get nvidia-settings to
recognize the HDMI and VGA outputs and have a dual-display mode on either (the
physical layout of the two ports prevented me from trying three screens).
In case anyone is interested, I was able to get mplayer to output stereo sound
through the HDMI cable as well. I used the following command:
mplayer -fomat s32le -ao alsa:device=hdmi=1.1 $FILENAME
The command
mplayer -format s32le -ao alsa:device=dmix=1.7 $FILENAME
also worked.
My video player of choice is VLC. In order to get it to output the sound to the
HDMI port, I went to Preferences/Audio, manually chose ALSA as the audio and
chose "HDA NVidia:HDMI 0 (hw:1,7)" as the device.
Please beware that it will take restarting VLC after saving these settings for
them to go into effect.
Next I'm going to work on cloning the audio output between the two cards (and
improving the HOWTO on the wiki).Original comment by lengau on 30 Dec 2010 at 3:53
GoogleCodeExporter
commented
9 years ago [deleted comment][deleted comment]Well I've been playing with the X settings a bit more and have come up with the
attached xorg.conf.
This version will talk to both the HDMI port and the VGA port.
Also, in messing around with the VGA and HDMI settings in nvidia-settings I
discovered that the chip will only output to one of the two at a time.
Also, thanks again to sigmadraconis for introducing me to disper. It's so much
easier to simply type 'disper -e' or 'disper -s' to get my display into the
right configuration than it is to use nvidia-settings all the time (especially
since the main reason I use a second display is for watching videos on my TV.
One thing I've noticed is that any use of nvidia-settings will cause disper to
spit out an error (I forget the exact wording, but it says 'Garbage metamode'
and refuses to do anything until I restart X). Not using nvidia-settings gets
around this.Original comment by lengau on 30 Dec 2010 at 7:45
Attachments:
GoogleCodeExporter
commented
9 years ago lengau, I forgot to mention one thing regarding the sound. It's much easier not
to change the VLC output if you have configured pulseaudio and redirect the
sound directly through the pulseaudio device chooser.
This problem is somewhat mixed with the (fixed) Issue 11 (
http://code.google.com/p/vaio-f11-linux/issues/detail?id=11 ).
First, when I ran the command "aplay -l", I had like 4 different HDMI outputs.
I notice that you have this problem because you had to redirect your VLC to the
hw:1.7 output, instead of using hw:1.3 like I used to). To make this work you
have to do these steps (ALWAYS BACKUP THE FILES YOU CHANGE SO YOU CAN FALL BACK
TO PREVIOUSE CONFIGURATIONS):
1) Edit the following file as sudo "/etc/modprobe.d/alsa-base.conf" and add the
following line to the end of the file (remember, I have a F13, not an F11 or an
F12, this works on my NVIDIA GT 425M, it may not work on GT 310M or GT 330M):
# HDMI - NVIDIA GT 425M
options snd-hda-intel probe_mask=0xffff,0xfff2
# IF THE ABOVE DOES NOT WORK, COMMENT THE ABOVE AND UNCOMMENT THE FOLLOWING LINE:
#options snd-hda-intel enable_msi=0 probe_mask=0xffff,0xfff2
This line will join all the HDMI devices in only one device. You need to
restart your distribution after running step 2) and then, run the command
"aplay -l". You will see that now you only have 1 HDMI device :)
2) Edit the file (or create it if it does not exist) "/etc/asound.conf" (don't
forget to backup!!!) and make sure you have these lines there:
pcm.pulse {
type pulse
}
ctl.pulse {
type pulse
}
pcm.!default {
type pulse
}
ctl.!default {
type pulse
}
You need to restart your machine after this step.
3) Change the following pulseaudio configuration file so the HDMI can be
detected successfully in the pulseaudio Volume Control. Edit the
"/etc/pulse/default.pa" file, go to the and add this line:
load-module module-alsa-sink device=hw:1,3
where the '3' SHOULD MATCH your "new" HDMI device id that you have in the
"aplay -l" list by now, if you successfully ran the 1). In the web page where I
get this they also recommended commenting out all of the module-udev-detect
section and adding similar lines like the above in the same section:
"load-module module-alsa-sink device=hw:0,0" and "load-module module-alsa-sink
device=hw:0,1" OR "load-module module-alsa-sink device=plughw:0,0" and
"load-module module-alsa-sink device=plughw:0,1".
I don't need to use the previous lines, just the first one that I isolated.
These previous lines are needed to tell pulseaudio that you also have those
devices, since commenting out the udev detection section will prevent
pulseaudio to grab those devices automatically from the UDEV.
4) Restart pulseaudio by running "pulseaudio --kill && pulseaudio" in the
command line.
That's it for configuring pulseaudio.
Now, to change the VLC output through pulseaudio instead of having to change it
in VLC and restart it, and considering that you have fixed your soundcard like
in all the previous steps
1) Install these packages: paman padevchooser pavucontrol pavumeter (*buntu:
sudo apt-get install paman padevchooser pavucontrol pavumeter)
2) Run "padevchooser" from the shell (or Alt+F2 in your window manager to run a
command), an icon will appear on system tray, choose Volume Control from there
(alternatively, you can also run "pavucontrol" from the shell).
3) Open VLC and try to run some video, you will see that in the Volume Control
application, in the Playback tab, you should see a new "VLC media player"
entry. Right to it, you have a button where you can change the output of VLC
(and any other app you want). You just have to change it to HDA NVIDIA, and
that's it!
This steps are easier than they look. If you try to google for some of mixed
words like "vaio sound probe_mask enable_msi"
I suspect that I can find a way to use the "pulseaudio" command to try and
redirect all the playback applications to the HDMI output, I just have to try
and find it, so I can add that method to the script I mentioned in my previous
post, so I can change the applications sound playback outputs (and output them
to the HDMI) in pulseaudio and also set the HDMI as the primary audio output,
so when launching new apps, these ones send their outputs to the HDMI also,
instead of the local soundcard.
This works for my Vaio F13Z1E, I cannot guarantee for any other, so backup your
files when trying this method! In attach are my own files I had to change
throughout this "tutorial".Original comment by sigmadra...@gmail.com on 30 Dec 2010 at 2:05
Attachments:
GoogleCodeExporter
commented
9 years ago 2011 january 10h : after an automatic update of Ubuntu 10.10 on my vaio
VPCF11S1E which broke again graphics, i made a new trial with
NVIDIA-Linux-x86_64-260.19.29.run taken from the nvidia website. It works !
(last stable version for me was NVIDIA-Linux-x86_64-260.53.run)
ref :
http://www.ubuntugeek.com/howto-install-nvidia-drivers-manually-on-ubuntu-10-04-
lucid-lynx.htmlOriginal comment by didier.v...@gmail.com on 10 Jan 2011 at 9:43
GoogleCodeExporter
commented
9 years ago Thanks to sigmadraconis (Comment 29), I was able to fix the HDMI sound problem
in my VPCF125FX with a 330M card. There was no need for me to comment out the
additional lines in step 3. I just modified the singled out line and it worked.
Thanks!Original comment by anna.kre...@gmail.com on 5 Jul 2011 at 1:11
Original issue reported on code.google.com by
stephv...@gmail.comon 11 Mar 2010 at 10:01Attachments: