On 04/13/2015 08:06 PM, Patrick Shanahan wrote: I am running Tumbleweed installed during the 12.0 days and continually

updated. I have an nvidia geforce gts 450 card with the nvidia driver 346.47. My monitor is an hdmi connected samsung 28 inch lcd with a second monitor hdmi connected vizio 50 inch lcd television.

All I did was plug in the hdmi cable and adjust settings using the "Display and Monitor" section from "systemsettings" for each monitor at one time or another.

Booting is a little odd as I do not normally have both monitors active. Booting gives me a green screen on my 28 inch with no prompt (it defaults no matter how I set it to the television). But blindly typing my user password provides access to the graphical environment. I do not have to power up the 50 inch display, just type the password.

This is just a guess to your problems as you fail to offer any discreption of your failure to boot. And I am certain that you tried the multi-user.target (non-graphical), and that you tried reversing the display connections, and that you tried with only one monitor attached.

Or are you discussing attaching an external monitor to a laptop? Or what is it that you want to know?

ps: opensuse will boot w/o *any* monitor attached. My server is configured that way, openSUSE 13.1.

Sorry for not being more complete. I posted this question once before without a solution. I have a Dell 1721 AMD laptop with an AMD/ATI RD690M {Radeon Express 1200/1250/1270] graphics controller. The system boots fine, as I think I suggested, but the sync on the monitors is wrong if I boot with the external VGA monitor plugged in. The monitors are garbled. If I unplug the external monitor, and ctrl-alt-backspace back to the X server, the laptop comes up clean. I can the add the second monitor as you described. My goal is to be able to boot the system using the external monitor only. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata wrote:

don fisher composed on 2015-04-13 20:39 (UTC-0700):

...

Sorry for not being more complete. I posted this question once before without a solution. I have a Dell 1721 AMD laptop with an AMD/ATI RD690M {Radeon Express 1200/1250/1270] graphics controller. The system boots

Earlier thread mentioned you also have Intel Graphics. ???

Earlier thread also implied you have two external monitors. Did you mean output/input ports when referring to trying HDMI instead of VGA or vice versa?

...

fine, as I think I suggested, but the sync on the monitors is wrong if I boot with the external VGA monitor plugged in. The monitors are garbled. If I unplug the external monitor, and ctrl-alt-backspace back to the X server, the laptop comes up clean. I can the add the second monitor as you described. My goal is to be able to boot the system using the external monitor only.

You still haven't clarified much in this thread.

When exactly does the garbling begin?

What are your displays' native resolutions? (2405FPW 16:10 1920x1200 external != UXGA; == WUXGA) (1721 Inspiron laptop 16:10 1440x900 != UXGA; )

Web specs I found about your laptop disagree whether 1920x1200 is also supported, or an optional native superceding 1440x900.

WXGA+ == 1440x900 UXGA == 1600x1200 WUXGA == 1920x1200

What does trying "unified outputs" mean?

AFAIR, that's an expression used in KDE when you're configuring two monitors. Ticking it mean using the same resolution on both monitors. (I was using a laptop with an external monitor over HDMI). -- Per Jessen, Zürich (10.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Anton Aylward composed on 2015-04-14 08:26 (UTC-0400):

Perhaps I'm reading too much into it, but Don seemed to imply that the X config was set at insulation and that was that, he couldn't edit it.

If he couldn't, maybe it was GUI tool at fault; could be https://bugs.kde.org/show_bug.cgi?id=317929 is blocking him. My read was that he thought he wasn't supposed to be able to use xorg.con* to do it, but also it sounded like in Fedora he got good results without any manual intervention like seems 13.2 is requiring. If the latter it could be that his Fedora was a string of updates rather than fresh installs that date back originally to before full automagic X configuration became the assumption. Remember, we used to use SaX2, which no longer esists, and SaX3 is limited in functionality.

As Felix says, yes it can be done and yes I've done customization, including dual monitors both live at boot (one portrait mode one one landscape mode).

Doing it here is routine, just not with the peculiarities of laptops involved, or guessing whether the primary screen's native mode is 1440x900 or 1920x1200. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 04/14/2015 10:53 AM, don fisher wrote:

I have been afraid to try to generate an xorg.conf for fear that the man pages and HowTo files were no longer available.

Right action, wrong reasoning. you don't use a "xorg.conf" any more. See under /etc/X11/xorg.conf.d/ The man pages for xorg.conf and xorg.conf.d are the same. Perhaps that page isn't clear enough about the use of /etc/X11/xorg.conf.d/ Googling shows up https://bbs.archlinux.org/viewtopic.php?id=129817 http://superuser.com/questions/438699/adding-dual-monitor-settings-to-xorg-c... which work through adding the entries in the monitor.conf for an extra display, and http://samuelmartin.wordpress.com/category/linux/ which is a bit more pedantic. Google is your friend :-) To be fair, when I did this, I experimented heavily with the xorg.conf.d files without bother much with reading how-tos. Experimenting and breaking things is a great way to learn :-) -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 04/13/2015 10:15 PM, Felix Miata wrote: Again, I was not complete. I have two classes of laptops. One is the Dell 1721 that has been the major subject of my inquire. The other is an Alienware 18, a magnificent creature, though rather huge to carry around:-) It has 3TB of hard disk, 32TGB ram, dual Nvidia 880 graphics hardware and a 4 core (=> 8 threads) 4GHz Intel CPU. I was introduced to openSuse while trying to find a replacement for the Fedora distribution that I was finding to be increasingly not user friendly. I did try also to connect the Alienware, which has HDMI outputs, to my Dell WUXGA monitor, using two different HDMI to VGA adapters. This experiment also failed. I currently have, and am writing this email from, the Alienware driving a Acer HDMI resolution external monitor, again using "Unified Outputs". This works great! On boot, the 1721 garbling begins when the system detects the presence of the monitor. It does not even have to be turned on! After booting without the monitor, I attach the monitor, go through the GUI setup, and the garbling starts when I touch the "Apply" button. When I looked at the Xorg log files, I did not see the entries I expected from the additions made in the GUI. But I may have missed something there. I did not see the "EE" which I believe is the error flag. I have tried a lot of things, and am always afraid of making emails too long. Sorry again for the omissions. Thanks, Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 04/14/2015 11:28 AM, Felix Miata wrote:

Three independent and unrelated things I'd like you to try separately only on the 1721:

1-During bootloader runtime, edit the default choice by appending to the kernel cmdline

video=1920x1200@60

If it helps, after trying the other suggestions following, reconfigure your bootloader to have it there always. For Grub2, you probably will not find any instructions explicitly telling you this is possible or desirable. Grub2 has its own way of producing the same effect that I'm not going to try to describe. For Grub Legacy, simply append it to the default stanza's kernel line in /boot/grub/menu.lst.

2-Disable compositing via Xorg. I do it with a file named

/etc/X11/xorg.conf.d/70-extensions.conf

containing:

Section "Extensions" Option "Composite" "Disable" EndSection

3-Disable KScreen. I do it by including in

~/.kde4/share/config/kdedrc

and/or

/etc/kde4/share/config/kdedrc

the following:

[Module-kscreen] autoload=false

Let us know which if any of these help before trying to build your own *xorg.con*.

Also provide /var/log/Xorg.0.log on http://susepaste.org/ or equivalent captured without any of these in place.

I was on the 1721 for awhile, so just got this email. What I have done is set systemd to leave me in multiuser mode. Then I executed startx and it appears to work, and took me into ICE window manger I think. I then modified my /root directory to match mine (.Xdefaults, .fvwm2rc, .xinitrc) and now I end up in FVWM2, which is where I like to work. So it appears that things get wrecked between the multiuser and graphical modes. The text screen still came up a bit of a mess, but when I executed startx everything was perfect. I will try your kernel switch and see if that helps. Does that switch apply to both screens? I need to find out how to run startx as a user so I do not have to mess in the root directory. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-04-14 22:20, Patrick Shanahan wrote:

* don fisher [04-14-15 16:09]: [...]

...

I need to find out how to run startx as a user so I do not have to mess in the root directory.

as <user>: /usr/bin/startx

really is not complicated ???

No, that doesn't work, wrong permissions. You have to change something in /etc/permissions.local. The comments there explains what, it is easy. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlUthNYACgkQja8UbcUWM1wO/wD+IiJ0Sg76A4J6ZVhY/Mb47MHs 4uGe/wty1dBeNXoCkfQA+wcpofhDaWN6bGpxecILUinKqDgvUwf2NowYSuBXfq1+ =OWOm -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-04-14 23:39, Felix Miata wrote:

Carlos E. R. composed on 2015-04-14 23:21 (UTC+0200):

It was easy, until suseconfig was retired, which was before 13.2 was released. Uncommenting that line in /etc/permissions.local hasn't done anything since.

permissions --> chkstat --system chkstat --system --set /sbin/set_polkit_default_privs (if change normal to secure, etc) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlUtkxgACgkQja8UbcUWM1x9pAD+IGJnA+8lDFV8IR7pZzkDVNmb MWwQ9oh6RBKPK5FH4b8A/3nUcFnDwTBEsW3hZfyhU7ChSnyFEkHxCfE9AvsFl3DJ =5au4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

don fisher composed on 2015-04-14 13:26 (UTC-0700):

X bombs with a message about not being SUID. Have not decoded the ramifications of that yet.

The clue to that is the last line in your /etc/permissions.local. 'chmod 4711 /usr/bin/Xorg' should remove that obstacle, but note the comment in that file above that last line. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

don fisher composed on 2015-04-14 13:07 (UTC-0700):

I will try your kernel switch and see if that helps. Does that switch apply to both screens?

AFAIK it absolutely should as long as both displays support the particular switch. In your case I'd be shocked if it did not. In trying to follow-up on https://bugzilla.kernel.org/show_bug.cgi?id=94171 I'm thinking there's some possibility it could apply to your case, manifesting as corruption instead of blackness. There you can see instead of using xorg.conf* I'm using a startup script in /etc/xinit/xinitrd.d/setup containing xrandr --dpi 144 --output DVI-0 --mode 1920x1080 --above VGA-0 --output VGA-0 --primary --mode 1920x1440 Converted to applicability to your 1721 would probably be something like xrandr --dpi 120 --output DVI-0 --mode 1920x1200 --above VGA-0 --output VGA-0 --primary --mode 1920x1920 You would need to grab the laptop's output name from Xorg.0.log to substitute for VGA-0, change --above to --left-of or --right-of to get side-by-side instead of over/under, and drop the --dpi 120 if tiny everything is your thing. Also for this to stick, Krandr or anything like it possibly used by FVWM2 would have to be disabled. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org