Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #160072 > unrolled thread

LXDE Display Coordination

Back to article view | Back to linux.debian.user

Contents

  LXDE Display Coordination ray <ray@aarden.us> - 2015-11-01 05:20 +0100
    Re: LXDE Display Coordination Charlie Kravetz <cjk@teamcharliesangels.com> - 2015-11-01 17:50 +0100
      Re: LXDE Display Coordination ray <ray@aarden.us> - 2015-11-01 20:30 +0100
        Re: LXDE Display Coordination Sven Arvidsson <sa@whiz.se> - 2015-11-01 20:40 +0100
        Re: LXDE Display Coordination Charlie Kravetz <cjk@teamcharliesangels.com> - 2015-11-01 22:00 +0100
    Re: LXDE Display Coordination Lisi Reisz <lisi.reisz@gmail.com> - 2015-11-01 18:20 +0100
      Re: LXDE Display Coordination ray <ray@aarden.us> - 2015-11-01 20:50 +0100
        Re: LXDE Display Coordination Felix Miata <mrmazda@earthlink.net> - 2015-11-02 09:10 +0100
          Re: LXDE Display Coordination ray <ray@aarden.us> - 2015-11-06 22:50 +0100
            Re: LXDE Display Coordination ray <ray@aarden.us> - 2015-11-07 05:00 +0100
              Re: LXDE Display Coordination Felix Miata <mrmazda@earthlink.net> - 2015-11-07 07:40 +0100
                Re: LXDE Display Coordination ray <ray@aarden.us> - 2015-11-07 17:00 +0100
                  Re: LXDE Display Coordination Felix Miata <mrmazda@earthlink.net> - 2015-11-07 17:30 +0100
                    Re: LXDE Display Coordination ray <ray@aarden.us> - 2015-11-08 04:50 +0100
                      Re: LXDE Display Coordination Felix Miata <mrmazda@earthlink.net> - 2015-11-08 06:20 +0100
                        Re: LXDE Display Coordination ray <ray@aarden.us> - 2015-11-08 16:20 +0100
                          Re: LXDE Display Coordination ray <ray@aarden.us> - 2015-11-08 18:30 +0100
                            Re: LXDE Display Coordination Felix Miata <mrmazda@earthlink.net> - 2015-11-08 18:40 +0100
                              Re: LXDE Display Coordination ray <ray@aarden.us> - 2015-11-11 02:50 +0100
                                Re: LXDE Display Coordination Felix Miata <mrmazda@earthlink.net> - 2015-11-11 03:30 +0100
                                  Re: LXDE Display Coordination Chris Bannister <cbannister@slingshot.co.nz> - 2015-11-11 07:40 +0100
                                    Re: LXDE Display Coordination Felix Miata <mrmazda@earthlink.net> - 2015-11-11 08:20 +0100
                                  Re: LXDE Display Coordination Brian <ad44@cityscape.co.uk> - 2015-11-11 07:50 +0100
                                  Re: LXDE Display Coordination Lisi Reisz <lisi.reisz@gmail.com> - 2015-11-11 13:40 +0100
                                    Re: LXDE Display Coordination Felix Miata <mrmazda@earthlink.net> - 2015-11-11 15:40 +0100
                                      Re: LXDE Display Coordination Charlie Kravetz <cjk@teamcharliesangels.com> - 2015-11-11 16:20 +0100
                                        Re: LXDE Display Coordination Lisi Reisz <lisi.reisz@gmail.com> - 2015-11-11 16:40 +0100
                                        Re: LXDE Display Coordination <tomas@tuxteam.de> - 2015-11-11 17:30 +0100
                                          Re: LXDE Display Coordination Chris Bannister <cbannister@slingshot.co.nz> - 2015-11-12 06:30 +0100
                                          Re: LXDE Display Coordination Brad Rogers <brad@fineby.me.uk> - 2015-11-12 09:30 +0100
                                            Re: LXDE Display Coordination Chris Bannister <cbannister@slingshot.co.nz> - 2015-11-12 13:00 +0100
                                            Re: LXDE Display Coordination Lisi Reisz <lisi.reisz@gmail.com> - 2015-11-12 13:40 +0100
                                        Re: LXDE Display Coordination Brian <ad44@cityscape.co.uk> - 2015-11-11 20:40 +0100
                                          Re: LXDE Display Coordination Felix Miata <mrmazda@earthlink.net> - 2015-11-11 21:10 +0100
                                    Re: LXDE Display Coordination Brian <ad44@cityscape.co.uk> - 2015-11-11 20:30 +0100
                                Re: LXDE Display Coordination Felix Miata <mrmazda@earthlink.net> - 2015-11-11 08:50 +0100
                                  Re: LXDE Display Coordination ray <ray@aarden.us> - 2015-11-12 03:10 +0100
                                    Re: LXDE Display Coordination Felix Miata <mrmazda@earthlink.net> - 2015-11-12 07:50 +0100
                                      Re: LXDE Display Coordination ray <ray@aarden.us> - 2015-11-13 03:50 +0100
                          Re: LXDE Display Coordination ray <ray@aarden.us> - 2015-11-08 19:10 +0100
                      Re: LXDE Display Coordination ray <ray@aarden.us> - 2015-11-08 16:00 +0100

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

#160424

On Tue, Nov 10, 2015 at 09:23:38PM -0500, Felix Miata wrote:
> >> Pastebin your current /boot/grub/grub.cfg
> 
> Pastebin means upload the information to
> 
> 	http://paste.debian.net/
> 
> or
> 
> 	http://pastebin.com/
> 
> or
> 
> 	http://paste.opensuse.org/
> 
> or
> 
> 	http://paste.ubuntu.com/
> 
> or equivalent, or to your own personal web space, and put a link thereto in
> your mailing list reply.
> 
> Pasting logs and configs into email puts it wasting space in the mailing list
> archive forever.
> 
> Pastebinning is temporary, a week or month or whatever the particular paste
> host is configured for.

So that means that searches through the archive will get a 404 instead
of the info which they're looking for. Seems a bit silly, don't you
think?

-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X

[toc] | [prev] | [next] | [standalone]

#160427

Chris Bannister composed on 2015-11-11 19:38 (UTC+1300):

> On Tue, Nov 10, 2015 at 09:23:38PM -0500, Felix Miata wrote:

>> Pasting logs and configs into email puts it wasting space in the mailing list
>> archive forever.

>> Pastebinning is temporary, a week or month or whatever the particular paste
>> host is configured for.

> So that means that searches through the archive will get a 404 instead
> of the info which they're looking for. Seems a bit silly, don't you
> think?

Not at all, as they're typically obsolete quickly, unlikely useful other than
for solving an OP's particular issues dependent on his unique hardware
configuration, looking for one or two short strings typically hard to
describe so that the help requester could ID and provide them within concise
context to prospective helpers.

When I'm doing the mailing list Googling, I skip those with long pastes or
attachments, trying to make my search time more effective by limiting
attention to those written with concision.

When stuff like full logs or grub.conf rather than snippits are attached to
or pasted in an email, I'm more likely to ignore them than work with them.
Typically, line wrapping done on an email sent makes a mess of things.
They're much more manageable in browser windows than email windows, and
separately from reply composition. And in this thread, the OP kept starting
his posts as if I were the only one he was writing to, so with no one else
continuing to try to help him, opportune time to make a request more likely
to enable me to do a better, or any, job helping further.
-- 
"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/

[toc] | [prev] | [next] | [standalone]

#160425

On Tue 10 Nov 2015 at 21:23:38 -0500, Felix Miata wrote:

> >> Pastebin your current /boot/grub/grub.cfg
> 
> Pastebin means upload the information to
> 
> 	http://paste.debian.net/
> 
> or
> 
> 	http://pastebin.com/
> 
> or
> 
> 	http://paste.opensuse.org/
> 
> or
> 
> 	http://paste.ubuntu.com/
> 
> or equivalent, or to your own personal web space, and put a link thereto in
> your mailing list reply.
> 
> Pasting logs and configs into email puts it wasting space in the mailing list
> archive forever.

No log or config which helps in solving a problem is wasted space.
A grub.cfg is not large.

> Pastebinning is temporary, a week or month or whatever the particular paste
> host is configured for.

Temporary means context is lost.

[toc] | [prev] | [next] | [standalone]

#160432

On Wednesday 11 November 2015 02:23:38 Felix Miata wrote:
> >> Pastebin your current /boot/grub/grub.cfg
>
> Pastebin means upload the information to
>
> 	http://paste.debian.net/
>
> or
>
> 	http://pastebin.com/
>
> or
>
> 	http://paste.opensuse.org/
>
> or
>
> 	http://paste.ubuntu.com/
>
> or equivalent, or to your own personal web space, and put a link thereto in
> your mailing list reply.
>
> Pasting logs and configs into email puts it wasting space in the mailing
> list archive forever.
>
> Pastebinning is temporary, a week or month or whatever the particular paste
> host is configured for.

Yes, so the archives are incomplete.  For shorter things it is surely better 
that they should be in the email and therefore available to those who search 
the archives.  /boot/grub/grub.cfg certainly counts as short in this context 
and I think it should therefore be in the email and searchable.

Lisi

[toc] | [prev] | [next] | [standalone]

#160434

Lisi Reisz composed on 2015-11-11 12:36 (UTC):

>> Pasting logs and configs into email puts it wasting space in the mailing
>> list archive forever.

>> Pastebinning is temporary, a week or month or whatever the particular paste
>> host is configured for.

> Yes, so the archives are incomplete.  For shorter things it is surely better 
> that they should be in the email and therefore available to those who search 
> the archives.  /boot/grub/grub.cfg certainly counts as short in this context 
> and I think it should therefore be in the email and searchable.

Ray's Xorg.0.log post was 38kb. His grub.cfg post was 26kb. I consider both
much too long to wade through in email archive searches. Help posts of under
10kb are nearly always more than sufficient.

Of course what any subscriber thinks doesn't really matter. Whatever a list's
rules permit is technically OK, even to including binary attachments, which I
usually delete unread, often even when sent from people in my address book.
-- 
"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/

[toc] | [prev] | [next] | [standalone]

#160440

On Wed, 11 Nov 2015 09:38:53 -0500
Felix Miata <mrmazda@earthlink.net> wrote:

>Lisi Reisz composed on 2015-11-11 12:36 (UTC):
>
>>> Pasting logs and configs into email puts it wasting space in the mailing
>>> list archive forever.  
>
>>> Pastebinning is temporary, a week or month or whatever the particular paste
>>> host is configured for.  
>
>> Yes, so the archives are incomplete.  For shorter things it is surely better 
>> that they should be in the email and therefore available to those who search 
>> the archives.  /boot/grub/grub.cfg certainly counts as short in this context 
>> and I think it should therefore be in the email and searchable.  
>
>Ray's Xorg.0.log post was 38kb. His grub.cfg post was 26kb. I consider both
>much too long to wade through in email archive searches. Help posts of under
>10kb are nearly always more than sufficient.
>
>Of course what any subscriber thinks doesn't really matter. Whatever a list's
>rules permit is technically OK, even to including binary attachments, which I
>usually delete unread, often even when sent from people in my address book.

I have to agree with Felix here. The more logs to wade through, the
less likely it will help someone else down the road. Have any of us
waded through all the logs just from this post? If so, congratulations!
You are much more patient than myself.


-- 
Charlie Kravetz
Linux Registered User Number 425914
[http://linuxcounter.net/user/425914.html]
Never let anyone steal your DREAM.   [http://keepingdreams.com]

[toc] | [prev] | [next] | [standalone]

#160441

On Wednesday 11 November 2015 15:12:11 Charlie Kravetz wrote:
> I have to agree with Felix here. The more logs to wade through, the
> less likely it will help someone else down the road. Have any of us
> waded through all the logs just from this post? If so, congratulations!
> You are much more patient than myself.

So you would have waded through them had they been on pastebin?

Lisi

[toc] | [prev] | [next] | [standalone]

#160444

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, Nov 11, 2015 at 08:12:11AM -0700, Charlie Kravetz wrote:

[...]

> I have to agree with Felix here [...]

I'm rather with "post here" -- if we are setting up a vote :-)

- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlZDYo8ACgkQBcgs9XrR2kYz7gCfa91SR8zJ4Rdj75GMG62jUsov
U7cAoIDSmyPoQ2zP/VeszXXvOPWH9VX/
=s5Vt
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#160466

On Wed, Nov 11, 2015 at 04:45:19PM +0100, tomas@tuxteam.de wrote:
> On Wed, Nov 11, 2015 at 08:12:11AM -0700, Charlie Kravetz wrote:
> 
> [...]
> 
> > I have to agree with Felix here [...]
> 
> I'm rather with "post here" -- if we are setting up a vote :-)

+1

-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X

[toc] | [prev] | [next] | [standalone]

#160472

[Multipart message — attachments visible in raw view] — view raw

On Wed, 11 Nov 2015 16:45:19 +0100
<tomas@tuxteam.de> wrote:

Hello tomas@tuxteam.de,

>I'm rather with "post here" -- if we are setting up a vote :-)

I'm all in favour of making it easy on the reader (not having to click
multiple links is a Good Thing), but that needs to be moderated by a
degree of reason:  I've seen some really silly behaviour - for example,
570kB images to relay information that could be conveyed in less than 10
words.  The irony there being that it takes longer to create the image
and attach it to an email than it does to just type the error message
into the MUA's editor.

Also, not everybody has an always on unlimited internet account.  For
those people, every byte counts.  So let's not forget their needs.

-- 
 Regards  _
         / )           "The blindingly obvious is
        / _)rad        never immediately apparent"
I hit the ground, boy have I arrived!
The History Of The World (Part 1) - The Damned

[toc] | [prev] | [next] | [standalone]

#160476

On Thu, Nov 12, 2015 at 08:28:31AM +0000, Brad Rogers wrote:
> On Wed, 11 Nov 2015 16:45:19 +0100
> <tomas@tuxteam.de> wrote:
> 
> Hello tomas@tuxteam.de,
> 
> >I'm rather with "post here" -- if we are setting up a vote :-)
> 
> I'm all in favour of making it easy on the reader (not having to click
> multiple links is a Good Thing), but that needs to be moderated by a
> degree of reason:  I've seen some really silly behaviour - for example,
> 570kB images to relay information that could be conveyed in less than 10
> words.  

Yeah, that's ridiculous. 

> Also, not everybody has an always on unlimited internet account.  For
> those people, every byte counts.  So let's not forget their needs.

I'm not. Are you suggesting that a person who sends a 570kB file without
a second thought, is going to bother using pastebin?

Another point I can think of, is if a person with a limited internet
account downloads an email but the link points to a 404, do you think
they're going to be pleased?

I personally would go WTF, what's the point of having the mailing list
archived at all! Come on guys, lets not throw common sense out the
window.

It's fine to post logs and configuration files to the mailing list, it's
been happening, like forever, no need to change it now.

-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X

[toc] | [prev] | [next] | [standalone]

#160480

On Thursday 12 November 2015 08:28:31 Brad Rogers wrote:
> Also, not everybody has an always on unlimited internet account.  For
> those people, every byte counts.  So let's not forget their needs.

So, as Chris said, let's all try to snip and do it well.  But if the full conf 
file is needed now in order to trouble shoot the problem, it will be needed 
by whoever finds the thread in the archives.

And I have snipped too much here.  I have not mastered the art of good 
snipping.

Lisi

[toc] | [prev] | [next] | [standalone]

#160451

On Wed 11 Nov 2015 at 08:12:11 -0700, Charlie Kravetz wrote:

> On Wed, 11 Nov 2015 09:38:53 -0500
> Felix Miata <mrmazda@earthlink.net> wrote:
> 
> >Lisi Reisz composed on 2015-11-11 12:36 (UTC):
> >
> >>> Pasting logs and configs into email puts it wasting space in the mailing
> >>> list archive forever.  
> >
> >>> Pastebinning is temporary, a week or month or whatever the particular paste
> >>> host is configured for.  
> >
> >> Yes, so the archives are incomplete.  For shorter things it is surely better 
> >> that they should be in the email and therefore available to those who search 
> >> the archives.  /boot/grub/grub.cfg certainly counts as short in this context 
> >> and I think it should therefore be in the email and searchable.  
> >
> >Ray's Xorg.0.log post was 38kb. His grub.cfg post was 26kb. I consider both
> >much too long to wade through in email archive searches. Help posts of under
> >10kb are nearly always more than sufficient.
> >
> >Of course what any subscriber thinks doesn't really matter. Whatever a list's
> >rules permit is technically OK, even to including binary attachments, which I
> >usually delete unread, often even when sent from people in my address book.
> 
> I have to agree with Felix here. The more logs to wade through, the
> less likely it will help someone else down the road. Have any of us

The less information provided, the easier it is to help someone?

> waded through all the logs just from this post? If so, congratulations!
> You are much more patient than myself.

Your lack of patience says nothing about the usefulness of the logs.

[toc] | [prev] | [next] | [standalone]

#160453

Brian composed on 2015-11-11 19:36 (UTC):

> The less information provided, the easier it is to help someone?

If s/less information provided/less noise provided/ then yes.
-- 
"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/

[toc] | [prev] | [next] | [standalone]

#160450

On Wed 11 Nov 2015 at 12:36:23 +0000, Lisi Reisz wrote:

> On Wednesday 11 November 2015 02:23:38 Felix Miata wrote:
> > >> Pastebin your current /boot/grub/grub.cfg
> >
> > Pastebin means upload the information to
> >
> > 	http://paste.debian.net/
> >
> > or
> >
> > 	http://pastebin.com/
> >
> > or
> >
> > 	http://paste.opensuse.org/
> >
> > or
> >
> > 	http://paste.ubuntu.com/
> >
> > or equivalent, or to your own personal web space, and put a link thereto in
> > your mailing list reply.
> >
> > Pasting logs and configs into email puts it wasting space in the mailing
> > list archive forever.
> >
> > Pastebinning is temporary, a week or month or whatever the particular paste
> > host is configured for.
> 
> Yes, so the archives are incomplete.  For shorter things it is surely better 
> that they should be in the email and therefore available to those who search 
> the archives.  /boot/grub/grub.cfg certainly counts as short in this context 
> and I think it should therefore be in the email and searchable.

I'd define short as an attachment or mail which does not exceed the size
allowed by listmaster@l.d.o. Compression can also be used.

[toc] | [prev] | [next] | [standalone]

#160428

ray composed on 2015-11-10 17:22 (UTC-0800):

>> what is output from

>> 	# 
> # cat /proc/cmdline
> placeholder root=/dev/mapper/mycomp--vg-root ro initrd=/install/gtk/initrd.gz quiet

Rather sparse, with nothing attempting to impact display configuration, other
than hiding init messages (quiet). Did you do that as user instead of root?
If not as root, do again as root.

>> what is output from

>> 	# fbset

> # fbset
> bash: fbset: command not found

# apt-get install fbset and try again.

>> Is your desired desktop result persisting across reboots?

> This is interesting.  It is persistent for the user this was setup under.  The other users have not changed to 1920x1080.  Note, root has 1920x1080 desktop from the original session shell command.  Note 2, the boot paramters for 1290x1080 have been removed.

How best to proceed depends on whether you want configuration done for only
individual user(s), or globally. If you want global, then everything done in
$HOME needs to be migrated out or eliminated.
-- 
"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/

[toc] | [prev] | [next] | [standalone]

#160462

Felix,

Thank you for descriptions.  

> > # cat /proc/cmdline
> > placeholder root=/dev/mapper/mycomp--vg-root ro initrd=/install/gtk/initrd.gz quiet
> 
> Rather sparse, with nothing attempting to impact display configuration, other
> than hiding init messages (quiet). Did you do that as user instead of root?
> If not as root, do again as root.

I do not recall inputting this line.  If I did change it, it must have been as root as the user doesn't have write access.

> > # fbset
> > bash: fbset: command not found
> 
> # apt-get install fbset and try again.

The output is:

mode "3840x2160"
    geometry 3840 2160 3840 2160 32
    timings 0 0 0 0 0 0 0
    accel true
    rgba 8/16,8/8,8/0,0/0
endmode



> > This is interesting.  It is persistent for the user this was setup under.  The other users have not changed to 1920x1080.  Note, root has 1920x1080 desktop from the original session shell command.  Note 2, the boot paramters for 1290x1080 have been removed.
> 
> How best to proceed depends on whether you want configuration done for only
> individual user(s), or globally. If you want global, then everything done in
> $HOME needs to be migrated out or eliminated.

I would like a global solution.  I am all the users.  After loosing login capabilities for a user on another installation, I set up two on this one.  Sure enough, the one I was working under lost graphic display.  So I immediately created two more.  Having a global solution, does have some risk.  If I blow it, I could loose all displays.  But the need for this solution is necessary, the screen is only readable with a magnifying glass at full resolution.  

So where to do I migrate the $HOME configuration?  
Is there a way to use /proc/cmdline to get the log on screen set to 1920x108?  

[toc] | [prev] | [next] | [standalone]

#160469

ray composed on 2015-11-11 17:46 (UTC-0800):

>> > # cat /proc/cmdline
>> > placeholder root=/dev/mapper/mycomp--vg-root ro initrd=/install/gtk/initrd.gz quiet

>> Rather sparse, with nothing attempting to impact display configuration, other
>> than hiding init messages (quiet). Did you do that as user instead of root?
>> If not as root, do again as root.

> I do not recall inputting this line.  If I did change it, it must have been as root as the user doesn't have write access.

>> > # fbset
>> > bash: fbset: command not found

>> # apt-get install fbset and try again.

> The output is:

> mode "3840x2160"
>     geometry 3840 2160 3840 2160 32
>     timings 0 0 0 0 0 0 0
>     accel true
>     rgba 8/16,8/8,8/0,0/0
> endmode

This is expected as a result of the absence of any video config options on
kernel cmdline. I just wanted to confirm this is what was actually occurring.

>> > This is interesting.  It is persistent for the user this was setup under.  The other users have not changed to 1920x1080.  Note, root has 1920x1080 desktop from the original session shell command.  Note 2, the boot paramters for 1290x1080 have been removed.

>> How best to proceed depends on whether you want configuration done for only
>> individual user(s), or globally. If you want global, then everything done in
>> $HOME needs to be migrated out or eliminated.

> I would like a global solution.  I am all the users.  After loosing login capabilities for a user on another installation, I set up two on this one.  Sure enough, the one I was working under lost graphic display.  So I immediately created two more.  Having a global solution, does have some risk.  If I blow it, I could loose all displays.  But the need for this solution is necessary, the screen is only readable with a magnifying glass at full resolution.  

> So where to do I migrate the $HOME configuration?   

Let's skip that methodology for now. Instead, ensure that ~/.screenlayout and
any other Xorg config changes you put in $HOME do not exist (rename, move,
etc.), then, save the following to /etc/X11/xorg.conf:

	http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.conf-ray

and restart *dm or reboot, login, then report results. If you don't get what
you expect or want, pastebin the resulting Xorg.0.log.

> Is there a way to use /proc/cmdline to get the log on screen set to 1920x108? 

There's supposed to be for Intel (worksforme), but let's defer that until
later too....
-- 
"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/

[toc] | [prev] | [next] | [standalone]

#160499

Felix,

Thank you, that worked great.

> This is expected as a result of the absence of any video config options on
> kernel cmdline. I just wanted to confirm this is what was actually occurring. 

I made the xorg.conf to put in the configuration.  But there is still no cmdline entry for this config.

I input:
lightdm restart
and there was no change.  So I rebooted and it worked.

[toc] | [prev] | [next] | [standalone]

#160319

Felix,

Here is an interesting twist.  I have reverted both grub and 00_header to the original (no 1920x1080 parameters) and executed update-grub2, and rebooted. The desktop comes in at 1920x1080.  Currently, the only artifacts directing 1920x1080 are the xrandr scripts in:
/home/user4/.config/autostart/eDP1_1920x1080.sh.desktop
/home/user4/.screenlayout/eDP1_1920x1080.sh

It would seem the grub functionality triggered something that xrandr did not.

[toc] | [prev] | [next] | [standalone]

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

Back to top | Article view | linux.debian.user

csiph-web