On Wed, May 31, 2017 at 3:44 PM, Allan Streib wrote:
>> You may be able to get a higher resolution by decreasing the refresh rate:
>>
>> $ gtf 2560 1440 33
>>
>> # 2560x1440 @ 33.00 Hz (GTF) hsync: 48.44 kHz; pclk: 162.77 MHz
>> Modeline "2560x1440_33.00" 162.77 2560 2688 2960 3360 1440 144
Sorry for the noise -- I hit send before I was finished formatting my
prior reply.
Maximilian Pichler writes:
> If and when I get my hands on another monitor I'll definitely try it
> out. (Although ultimately it would be nice to get it working with this
> one, as it works fine under Linux. This
Maximilian Pichler writes:
> If and when I get my hands on another monitor I'll definitely try it
> out. (Although ultimately it would be nice to get it working with this
> one, as it works fine under Linux. This is a Dell U2515H.)
Interesting, that's the same model I have.
You may be able
On Wed, May 31, 2017 at 2:06 PM, Allan Streib wrote:
> I think you should try another monitor if at all possible. Perhaps your
> monitor just goes into power-save mode with an incompatible signal.
If and when I get my hands on another monitor I'll definitely try it
out. (Although ultimately it wo
Maximilian Pichler writes:
> Just tried another graphics card (VisionTek Radeon HD 6350), with
> identical results: the boot messages are shown, then the signal is
> lost.
>
I think you should try another monitor if at all possible. Perhaps your
monitor just goes into power-save mode with an inc
Just tried another graphics card (VisionTek Radeon HD 6350), with
identical results: the boot messages are shown, then the signal is
lost.
On Wed, May 31, 2017 at 1:02 AM, Luis Coronado wrote:
> xrandr over ssh? even if you run it with -X it will display something from
> the machine running the ssh client (and the local X server) not the ssh
> server one :s
>
> -l
>
> On Tue, May 30, 2017 at 3:08 PM, Mihai Popescu wrote:
>>
>> What
xrandr over ssh? even if you run it with -X it will display something from
the machine running the ssh client (and the local X server) not the ssh
server one :s
-l
On Tue, May 30, 2017 at 3:08 PM, Mihai Popescu wrote:
> What is the output of xrandr plain command, without any parameters? Do
> no
Without parameters, via ssh:
$ xrandr
Can't open display
$ echo [$DISPLAY]
[]
This is after logging in and typing startx on the keyboard, with a
blank monitor. I've also tried launching startx via ssh, with the same
result.
On Tue, May 30, 2017 at 5:08 PM, Mihai Popescu wrote:
> What is the out
What is the output of xrandr plain command, without any parameters? Do
not use display numbers or anything else, type it like this 'xrandr'
using a ssh connection on the non working configuration.
On Tue, May 30, 2017 at 2:55 PM, Mihai Popescu wrote:
> Did you disable the onboard card from BIOS? What options do you have for this?
In the BIOS, "Primary Graphics Adapter" is set to "PCI Express". When
switching it to "Onboard" and plugging the cable into the onboard DP,
the boot message and t
> (by accident I had the cable connected to the onboard video)
I recall I tried once a dual monitor setup using an onboard graphics +
another plugged in card. I don't remember exactly, but I think the
boot message was shown one the onboard graphic card only or on both
monitors. I was concerned abo
On Tue, May 30, 2017 at 2:15 PM, wrote:
> Just a thought -- maybe it's because there is no error ???
>
> man xbacklight(1)
$ xbacklight
No outputs have backlight property
The monitor is not just dark, but it says "no signal" and goes into
power save mode.
On Tue, May 30, 2017 at 12:22:09PM -0400, Maximilian Pichler wrote:
As mentioned, I booted another OS from a USB stick and it runs at
2560x1440@60MHz. Doesn't this make it unlikely that the issue is with
the monitor or cable? Also, the connection is via DisplayPort, even
the most basic version of
I would certainly have followed Allan's advice, but only own one
monitor. Apologies for having failed to mention this.
> Is there not a more systematic way of debugging this?
IT is, but it may be different than your method.
> I find it puzzling that none of the logs contains any error message.
I find it puzzling asking about a problem on a list and not following
any of the advices and report back. I will find it
As mentioned, I booted another OS from a USB stick and it runs at
2560x1440@60MHz. Doesn't this make it unlikely that the issue is with
the monitor or cable? Also, the connection is via DisplayPort, even
the most basic version of which shouldn't struggle with this
resolution.
Is there not a more s
Maximilian Pichler writes:
>2560x1440 59.95*+
>2048x1152 60.00
>1920x1200 59.88
>1920x1080 60.0050.0059.9430.0025.0024.00
[...]
Try connecting a lower-resolution monitor and see if it works, if you
have one.
I have found that my dual 2560x144
Apologies, I have to revise the results from my previous message (by
accident I had the cable connected to the onboard video).
In fact xrandr does detect the DisplayPort connection:
$ DISPLAY=:0 xrandr
Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
DisplayPort-0 connected p
"Jens A. Griepentrog" writes:
> Is there a way to choose lower resolutions for radeondrm console using
> some suitable configuration file?
I asked basically this question some weeks ago, and lack of any answer
and not finding anything about this in man pages or FAQ has me to belive
that for now
I tried your suggestion of logging in with the keyboard while the
screen is blank and then typing "startx". Then logged in via ssh:
$ DISPLAY=:0 xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
DisplayPort-0 disconnected primary (normal left inverted right x axis y axis)
On Sun, May 28, 2017 at 4:50 PM, Steven McDonald
wrote:
> Have you tried booting more than once?
Yes, many times, both warm and cold.
On 05/28/17 22:50, Steven McDonald wrote:
On Sun, 28 May 2017 15:37:08 -0400
Maximilian Pichler wrote:
After the installation of a VisionTek Radeon 5450 graphics card my
machine gives a blank screen after booting. It still shows the normal
system messages (full dmesg below), with the last visi
On Sun, 28 May 2017 22:54:22 +0200
Steven McDonald wrote:
> Re-reading your mail, it sounds like you installed the card into an
> existing system. In that case, my question becomes "have you run
> fw_update?"
Just noticed the part of your mail where you showed you had the
firmware installed. Sor
Re-reading your mail, it sounds like you installed the card into an
existing system. In that case, my question becomes "have you run
fw_update?"
On Sun, 28 May 2017 15:37:08 -0400
Maximilian Pichler wrote:
> After the installation of a VisionTek Radeon 5450 graphics card my
> machine gives a blank screen after booting. It still shows the normal
> system messages (full dmesg below), with the last visible one being
> "scsibus4 at softraid0:
Hi,
After the installation of a VisionTek Radeon 5450 graphics card my
machine gives a blank screen after booting. It still shows the normal
system messages (full dmesg below), with the last visible one being
"scsibus4 at softraid0: 256 targets". Then the monitor (connected via
DisplayPort) goes i
27 matches
Mail list logo
