On 01/25/2017 10:01 AM, Massimo Canonico wrote:
> If someone has a similar problem, I suggest to read this page:
>
> https://wiki.archlinux.org/index.php/HiDPI
>
> It helps me a lot, but I'm still having problem with the monitors.
> Zooming/panning make the display blurry and (as suggested in
If someone has a similar problem, I suggest to read this page:
https://wiki.archlinux.org/index.php/HiDPI
It helps me a lot, but I'm still having problem with the monitors.
Zooming/panning make the display blurry and (as suggested in the web
page) I should try to adjust the "sharpness"
Hi all,
I've bought a new laptop (Dell xps 13.3) and the monitor resolution is
3200x1800. Now the problem is that I cannot use this laptop with my
external monitor which I use as an extended monitor. The external
monitor could reach 1280x1024. So when I try to move a window from the
laptop
On Mon, Nov 25, 2013 at 5:50 PM, Richard Sewill rsew...@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
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
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
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
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
--
http://www.qrz.com/db/W2BOD
Box 10
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
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
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,
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 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
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
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
I have a ViewSonic VX2035wm LCD Display monitor on this computer that is
not recognized by Fedora-18. 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
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
On 03/03/13 05:57, Bob Goodwin - Zuni, Virginia, USA wrote:
On 03/03/2013 04:57 AM, Marko Vojinovic wrote:
Ok, this is the relevant portion of the file:
[31.968] (II) RADEON(0): EDID for output VGA-0
[31.968] (II) RADEON(0): Printing probed modes for output VGA-0
[31.968] (II)
On Sat, 02 Mar 2013 14:24:57 -0500
Bob Goodwin - Zuni, Virginia, USA bobgood...@wildblue.net wrote:
On 03/02/2013 01:40 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
On 03/02/2013 04:24 AM, Marko Vojinovic wrote:
If it was a clean install, you should send us the content
of
On 03/03/2013 04:57 AM, Marko Vojinovic wrote:
Ok, this is the relevant portion of the file:
[31.968] (II) RADEON(0): EDID for output VGA-0
[31.968] (II) RADEON(0): Printing probed modes for output VGA-0
[31.968] (II) RADEON(0): Modeline 1024x768x60.0 65.00 1024
1048 1184 1344
On Fri, 01 Mar 2013 16:49:56 -0500
Bob Goodwin - Zuni, Virginia, USA bobgood...@wildblue.net wrote:
Section Device
Identifier Videocard0
Driver ati
I wonder if the ati driver is appropriate. The processor is an AMD A8
3850 and the GPU is apparently
On Fri, 01 Mar 2013 18:41:41 -0500
David dgbo...@gmail.com wrote:
You could use system-config-display to do this. But Fedora dropped
it several releases ago.
Did you ever get well informed about *why* it was dropped? There was a
reason for that.
And now is when you will get message after
Allegedly, on or about 02 March 2013, Marko Vojinovic sent:
or with a faulty VGA cable
Or, just so nobody is left in the lurch, an apparently not faulty brand
new cable, that simply hasn't got any wiring between the two pins that
carry the EDID signals. Some cheap cables only bother wire up
On Sat, 02 Mar 2013 21:18:21 +1030
Tim ignored_mail...@yahoo.com.au wrote:
Allegedly, on or about 02 March 2013, Marko Vojinovic sent:
or with a faulty VGA cable
Or, just so nobody is left in the lurch, an apparently not faulty
brand new cable, that simply hasn't got any wiring between
On 03/02/2013 12:36 AM, poma wrote:
ls -l /sys/class/drm/
poma
[bobg@box10 ~]$ ls -l /sys/class/drm/
total 0
lrwxrwxrwx. 1 root root0 Mar 2 2013 card0 -
../../devices/pci:00/:00:01.0/drm/card0
lrwxrwxrwx. 1 root root0 Mar 2 2013 card0-HDMI-A-1 -
On 03/02/13 13:32, Bob Goodwin - Zuni, Virginia, USA wrote:
On 03/02/2013 12:36 AM, poma wrote:
ls -l /sys/class/drm/
poma
[bobg@box10 ~]$ ls -l /sys/class/drm/
total 0
lrwxrwxrwx. 1 root root0 Mar 2 2013 card0 -
../../devices/pci:00/:00:01.0/drm/card0
lrwxrwxrwx. 1 root
On 03/02/2013 04:24 AM, Marko Vojinovic wrote:
Well, first of all, you probably want to put radeon driver up there
instead of ati.
Did that ...
Second, the data about your PCI hardware, including the graphics card,
is displayed by lspci -v, which should confirm that you have an ATI
Radeon
On 03/02/2013 04:24 AM, Marko Vojinovic wrote:
If it was a clean install, you should send us the content
of /var/log/Xorg.0.log file (it may be large, maybe put it in a pastebin
or something). This file can tell all the details about what is going
wrong with automatic resolution detection and
On 03/02/2013 01:40 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
On 03/02/2013 04:24 AM, Marko Vojinovic wrote:
If it was a clean install, you should send us the content
of /var/log/Xorg.0.log file (it may be large, maybe put it in a pastebin
or something). This file can tell all the details
On 03/01/2013 12:48 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
In a new Fedora-18/64 bit install in a new computer I am unable to set
the resolution above 1024x768 at 60HZ and would like to set it higher.
Just for grins, have you tried without any conf file at all? I don't
have one, and X
On 03/02/2013 03:49 PM, Thomas Cameron wrote:
On 03/01/2013 12:48 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
In a new Fedora-18/64 bit install in a new computer I am unable to set
the resolution above 1024x768 at 60HZ and would like to set it higher.
Just for grins, have you tried without
In a new Fedora-18/64 bit install in a new computer I am unable to set
the resolution above 1024x768 at 60HZ and would like to set it higher.
I found the following:.
[root@box10 ~]# ll /etc/X11/xorg.conf.d
total 4
-rw-rw-r--. 1 root root 161 Feb 28 04:42 00-anaconda-keyboard.conf
To which I
On 03/01/2013 06:48 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
In a new Fedora-18/64 bit install in a new computer I am unable to set
the resolution above 1024x768 at 60HZ and would like to set it higher.
I found the following:.
[root@box10 ~]# ll /etc/X11/xorg.conf.d
total 4
On 03/01/2013 02:42 PM, g wrote:
give this a try:
Section Monitor
Identifier Monitor0
EndSection
Section Device
Identifier Videocard0
Driver ati
EndSection
Section Screen
Identifier Screen0
Device
On 03/02/13 05:49, Bob Goodwin - Zuni, Virginia, USA wrote:
ell that's an improvement in that it works however I still don't have an
option of selecting higher than 1024x768.
Section Device
Identifier Videocard0
Driver ati
I wonder if the ati driver is
On 03/01/2013 09:49 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
On 03/01/2013 02:42 PM, g wrote:
give this a try:
cutting that out. sending full layout.
Well that's an improvement in that it works however I still don't have
an option of selecting higher than 1024x768.
Section Device
On 3/1/2013 1:48 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
In a new Fedora-18/64 bit install in a new computer I am unable to set
the resolution above 1024x768 at 60HZ and would like to set it higher.
I found the following:.
[root@box10 ~]# ll /etc/X11/xorg.conf.d
total 4
On 03/01/2013 06:29 PM, Ed Greshko wrote:
Time for the usual questions.
What is the output of xrandr? And, is your monitor attached to your system
via a KVM switch?
--
[bobg@box10 ~]$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
VGA-0 connected
On 03/01/2013 06:40 PM, g wrote:
i was not familiar with the amd a8-3850 cpu/gpu. a quick search via
ixquick.com [i am thru with gobble and their tracking] to find out a
little more about the cpu/gpu chip. nothing to say how it appears.
amd now owns ati, so your driver ?should? be correct. or
On 03/01/2013 06:41 PM, David wrote:
You could use system-config-display to do this. But Fedora dropped
it several releases ago.
And now is when you will get message after message chock full of helpful
'try this' suggestions that won't work and many 'what does some cryptic
CLI command say?
On 3/1/2013 7:11 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
On 03/01/2013 06:41 PM, David wrote:
You could use system-config-display to do this. But Fedora dropped
it several releases ago.
And now is when you will get message after message chock full of helpful
'try this' suggestions
On 03/02/13 00:55, Bob Goodwin - Zuni, Virginia, USA wrote:
On 03/01/2013 06:29 PM, Ed Greshko wrote:
Time for the usual questions.
What is the output of xrandr? And, is your monitor attached to your
system via a KVM switch?
--
[bobg@box10 ~]$ xrandr
Screen 0: minimum 320 x 200,
42 matches
Mail list logo
