CORRECTION: Fedora-19
I have a ViewSonic VX2035wm LCD Display monitor on this computer that is not recognized by Fedora-19. in order to get a reasonable display I have to run /usr/bin/xrandr -s 1680x1050 after I am logged in and the display [XFCE] is running. That works for me but it seems a bit clunky and after doing so for more than a year I would like to find some more elegant way to deal with it.
I could use a different monitor but I prefer the aspect ratio of this one, it's wide but higher than the others available.
Anyone know a better way to deal with this? As it stands it is just one of the things I do every morning after booting the computer ...
Bob
On 24.11.2013 17:00, Bob Goodwin - Zuni, Virginia, USA wrote:
CORRECTION: Fedora-19
I have a ViewSonic VX2035wm LCD Display monitor on this computer that is not recognized by Fedora-19. in order to get a reasonable display I have to run /usr/bin/xrandr -s 1680x1050 after I am logged in and the display [XFCE] is running. That works for me but it seems a bit clunky and after doing so for more than a year I would like to find some more elegant way to deal with it.
I could use a different monitor but I prefer the aspect ratio of this one, it's wide but higher than the others available.
Anyone know a better way to deal with this? As it stands it is just one of the things I do every morning after booting the computer ...
This question is already answered in detail.
poma
On 11/25/2013 04:39 AM, poma wrote:
On 24.11.2013 17:00, Bob Goodwin - Zuni, Virginia, USA wrote:
Anyone know a better way to deal with this? As it stands it is just one of the things I do every morning after booting the computer ...
This question is already answered in detail.
poma
Ok, then I assume that to mean there is no better way.
This message is an interesting experiment in that I have copied your response between Thunderbird in this F-19 computer to Thunderbird in the VMware F-20 beta virtual machine. Hopefully it will still thread properly?
Thanks,
Bob
On 25.11.2013 17:27, Bob Goodwin - Zuni, Virginia, USA wrote:
Ok, then I assume that to mean there is no better way.
Please this time try to read carefully from top to bottom. http://thread.gmane.org/gmane.linux.redhat.fedora.general/425665
This message is an interesting experiment in that I have copied your response between Thunderbird in this F-19 computer to Thunderbird in the VMware F-20 beta virtual machine. Hopefully it will still thread properly?
U2 should know better after years of use. F20 ain't an official, so https://admin.fedoraproject.org/mailman/listinfo/test
poma
On 25/11/13 12:29, poma wrote:
On 25.11.2013 17:27, Bob Goodwin - Zuni, Virginia, USA wrote:
Ok, then I assume that to mean there is no better way.
Please this time try to read carefully from top to bottom. http://thread.gmane.org/gmane.linux.redhat.fedora.general/425665
Ok, so I have done the following [I think]:
Automation in da display manager style: /etc/lightdm/lightdm.conf: display-setup-script=/usr/bin/RandR …
/usr/bin/RandR: #!/bin/sh # ViewSonic VX2035wm xrandr --newmode "1680x1050R" 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync >/dev/null 2>&1 xrandr --addmode VGA-0 1680x1050R >/dev/null 2>&1 xrandr --output VGA-0 --mode 1680x1050R >/dev/null 2>&1 exit 0
Cheers, poma
Then when I select the "Display" GUI it offers me 1680x1050 sure enough but does not actually select it.
I still have to run my script to get other than 1024x768.
It doesn't seem to pay attention to lightdm.conf?
This message is an interesting experiment in that I have copied your response between Thunderbird in this F-19 computer to Thunderbird in the VMware F-20 beta virtual machine. Hopefully it will still thread properly?
U2 should know better after years of use. F20 ain't an official, so https://admin.fedoraproject.org/mailman/listinfo/test
So I can't even mention it when I am testing to see if I can move one message between F-19 and it and maintain the threading? Which it did incidentally!
Bob
poma
On 25.11.2013 22:23, Bob Goodwin - Zuni, Virginia, USA wrote:
Then when I select the "Display" GUI it offers me 1680x1050 sure enough but does not actually select it.
I still have to run my script to get other than 1024x768.
It doesn't seem to pay attention to lightdm.conf?
"--output" selects a particular output mode, so it should work. Move a 'monitors.xml' so it doesn't interfere with setup, $ mv $HOME/.config/monitors.xml $HOME/.config/monitors.xml-backup and disable that session script of yours. Check what's happening via '/var/log/lightdm/lightdm.log'
So I can't even mention it when I am testing to see if I can move one message between F-19 and it and maintain the threading? Which it did incidentally!
You are probably the oldest dude here and intelligent, so please prefer to be a positive example for all of us.
poma
On 25/11/13 18:28, poma wrote:
"--output" selects a particular output mode, so it should work. Move a 'monitors.xml' so it doesn't interfere with setup, $ mv $HOME/.config/monitors.xml $HOME/.config/monitors.xml-backup and disable that session script of yours. Check what's happening via '/var/log/lightdm/lightdm.log'
"locate *monitors.xml" produces nothing, perhaps that is present only in gnome3? I believe this F-19 began as an XFCE Live spin.
But no, it doesn't show up in an "unnamed" later version, that does include Gnome3, either? So I'm not sure where you are getting those .xml files from?
My script only runs when I initiate it, I test before running it.
"/var/log/lightdm/lightdm.log" contains a lot of data but I'm not sure what I should look for, nothing "jumps out at me."
Bob
On 26.11.2013 18:06, Bob Goodwin - Zuni, Virginia, USA wrote:
On 25/11/13 18:28, poma wrote:
"--output" selects a particular output mode, so it should work. Move a 'monitors.xml' so it doesn't interfere with setup, $ mv $HOME/.config/monitors.xml $HOME/.config/monitors.xml-backup and disable that session script of yours. Check what's happening via '/var/log/lightdm/lightdm.log'
"locate *monitors.xml" produces nothing, perhaps that is present only in gnome3? I believe this F-19 began as an XFCE Live spin.
But no, it doesn't show up in an "unnamed" later version, that does include Gnome3, either? So I'm not sure where you are getting those .xml files from?
You're right. 'xfce4-display-settings' saves the settings in the $HOME/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml Désolé.
My script only runs when I initiate it, I test before running it.
Can you paste the content of that script, here.
"/var/log/lightdm/lightdm.log" contains a lot of data but I'm not sure what I should look for, nothing "jumps out at me."
Feel free to paste the content of the 'lightdm.log' at http://fpaste.org so it can be studied. If you do, one for the "RandR" round, and one for the script of yours. One copy you can send to the Vogons.
poma
On 26/11/13 16:38, poma wrote:
Feel free to paste the content of the 'lightdm.log' athttp://fpaste.org so it can be studied. If you do, one for the "RandR" round, and one for the script of yours. poma
Ok, it looks like it sent it to http://ur1.ca/g3pzw
On 26.11.2013 23:58, Bob Goodwin - Zuni, Virginia, USA wrote:
Ok, it looks like it sent it to http://ur1.ca/g3pzw
Thy 'lightdm.log': [+1.00s] DEBUG: Got signal from X server :0 [+1.00s] DEBUG: Connecting to XServer :0 [+1.00s] DEBUG: Starting greeter [+1.01s] DEBUG: Started session 974 with service 'lightdm-greeter', username 'lightdm'
My 'lightdm.log': [+0.50s] DEBUG: DisplayServer x-0: Got signal from X server :0 [+0.50s] DEBUG: DisplayServer x-0: Connecting to XServer :0 [+0.50s] DEBUG: Launching process 2099: /usr/bin/RandR [+0.80s] DEBUG: Process 2099 exited with return value 0 [+0.81s] DEBUG: Seat: Exit status of /usr/bin/RandR: 0 [+0.81s] DEBUG: Seat: Display server ready, starting session authentication [+0.81s] DEBUG: Session: Setting XDG_VTNR=1 [+0.81s] DEBUG: Session pid=2105: Started with service 'lightdm-greeter', username 'lightdm'
Notice an important difference in logs.
poma
In addition:
$ lightdm -v lightdm 1.9.2
/etc/lightdm/lightdm.conf: [SeatDefaults] display-setup-script=/usr/bin/RandR
/usr/bin/RandR: #!/bin/sh PATH="/usr/bin:$PATH"
xrandr --newmode "1680x1050R" 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync xrandr --addmode DVI-I-1 1680x1050R xrandr --output DVI-I-1 --mode 1680x1050R
exit 0
$ stat -c %a /usr/bin/RandR 755
I hesitate trying to answer this question because what I am doing may be wrong.
I tried the following on F18.
I edited the line, found in file /etc/default/grub, which starts GRUB_CMDLINE_LINUX="rd.md=0 ... rhgb quiet" appending strings so it had GRUB_CMDLINE_LINUX="rd.md=0 ... rhgb quiet" drm_kms_helper.edid_firmware=edid/1024x768.bin video=VGA-1:e
I next edited any existing lines in /boot/grub2/grub.cfg that had the string "rhgb quiet" to include the drm_kms_helper.edid_firmware=edid/1024x768.bin video=VGA-1:e string which I since learned is the wrong things to do.
From my limited understanding, /boot/grub2/grub.cfg is auto-generated using
/etc/default/grub each time /boot/grub2/grub.cfg is recreated. I should have used the grub2-mkconfig command instead of editing /boot/grub2/grub.cfg directly.
I got this idea reading https://wiki.archlinux.org/index.php/Kernel_Mode_Setting#Forcing_modes_and_E... and https://www.osadl.org/Single-View.111+M5b7fe294ea7.0.html
In my case I wish to run a headless server, but wish to have Linux believe there is a certain size window if I vnc into the server using x11vnc on the server. My vnc client happens to run on a laptop with a screen size, 1024x768.
I do not know if you need the video=VGA-1:e because you indicated you have a monitor connected. I do not know if you can use one of the four standard timings that are hard-coded in the driver. Please note: there are notes saying this works only with certain drivers. I am using the nouveau driver. I don't know if this works if you are using the nvidia driver; a note in one of the URLs said it did not work with the nvidia driver at one time.
Please save any files before editing. You and I don't know if this will work for you. It's best to play it safe and have backups just in case.
On 25/11/13 12:50, Richard Sewill wrote:
I hesitate trying to answer this question because what I am doing may be wrong.
I tried the following on F18.
I edited the line, found in file /etc/default/grub, which starts GRUB_CMDLINE_LINUX="rd.md=0 ... rhgb quiet" appending strings so it had GRUB_CMDLINE_LINUX="rd.md=0 ... rhgb quiet" drm_kms_helper.edid_firmware=edid/1024x768.bin video=VGA-1:e
I next edited any existing lines in /boot/grub2/grub.cfg that had the string "rhgb quiet" to include the drm_kms_helper.edid_firmware=edid/1024x768.bin video=VGA-1:e string which I since learned is the wrong things to do.
From my limited understanding, /boot/grub2/grub.cfg is auto-generated using /etc/default/grub each time /boot/grub2/grub.cfg is recreated. I should have used the grub2-mkconfig command instead of editing /boot/grub2/grub.cfg directly.
I got this idea reading https://wiki.archlinux.org/index.php/Kernel_Mode_Setting#Forcing_modes_and_E... and https://www.osadl.org/Single-View.111+M5b7fe294ea7.0.html
In my case I wish to run a headless server, but wish to have Linux believe there is a certain size window if I vnc into the server using x11vnc on the server. My vnc client happens to run on a laptop with a screen size, 1024x768.
I do not know if you need the video=VGA-1:e because you indicated you have a monitor connected. I do not know if you can use one of the four standard timings that are hard-coded in the driver. Please note: there are notes saying this works only with certain drivers. I am using the nouveau driver. I don't know if this works if you are using the nvidia driver; a note in one of the URLs said it did not work with the nvidia driver at one time.
Please save any files before editing. You and I don't know if this will work for you. It's best to play it safe and have backups just in case.
Thanks for your thoughts. This may work but I am hesitant to go too far in experimenting for fear of not being able to boot the computer which is always a bother ... What I have works, I was hoping someone knew of a better way that had worked for them.
Bob
On Mon, Nov 25, 2013 at 5:50 PM, Richard Sewill rsewill@gmail.com wrote:
I hesitate trying to answer this question because what I am doing may be wrong.
I tried the following on F18.
I edited the line, found in file /etc/default/grub, which starts GRUB_CMDLINE_LINUX="rd.md=0 ... rhgb quiet" appending strings so it had GRUB_CMDLINE_LINUX="rd.md=0 ... rhgb quiet" drm_kms_helper.edid_firmware=edid/1024x768.bin video=VGA-1:e
I next edited any existing lines in /boot/grub2/grub.cfg that had the string "rhgb quiet" to include the drm_kms_helper.edid_firmware=edid/1024x768.bin video=VGA-1:e string which I since learned is the wrong things to do.
From my limited understanding, /boot/grub2/grub.cfg is auto-generated using /etc/default/grub each time /boot/grub2/grub.cfg is recreated. I should have used the grub2-mkconfig command instead of editing /boot/grub2/grub.cfg directly.
I can't comment about the actual options but they won't be included in GRUB_CMDLINE_LINUX if you don't include them within the quotes as you've done:
"rd.md=0 ... rhgb quiet" drm_kms_helper.edid_firmware=edid/1024x768.bin video=VGA-1:e
You need:
"rd.md=0 ... rhgb quiet drm_kms_helper.edid_firmware=edid/1024x768.bin video=VGA-1:e"
-
Bob Goodwin -
poma -
Richard Sewill -
Tom H