xrandr will not detect monitor on DisplayPort [closed]
Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
I recently got a new ViewSonic Monitor and was configuring it to 144 Hz using XRandr. It seems I messed something up and now, I can't get my monitor to work using DisplayPort. Only HDMI works.
This issue started after I typed xrandr --output DP-0 --mode 2560x1440 --rate 144.00 into terminal and moved the mouse. The screen said "no signal". I turned the monitor and computer on and off and nothing happened. Switching to HDMI fixes the problem but then I can't use the 144 Hz. I think this is a Linux related issue and not a monitor related issue since the problem started after I edited the xrandr code. The only thing I can think of is changing the xrandr setting again but I can't do that since xrandr says that DP-0 is disconnected.
I have tried:
- Changing XRandr setting
- switching out DP cables
- Clearing monitor settings file
Edit: I just noticed that when I turn my computer on with DP-0 plugged in, my monitor briefly reacts before going into standby mode. Turning it on still says "No signal".
linux ubuntu xrandr monitors resolution
asked Oct 29 '17 at 18:23
Dan
216
closed as off-topic by Jeff Schaller, Stephen Rauch, G-Man, Archemar, Anthony Geoghegan Nov 12 '17 at 22:33
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Jeff Schaller, Stephen Rauch, G-Man, Archemar, Anthony Geoghegan
add a comment |Â
up vote
2
down vote
favorite
I recently got a new ViewSonic Monitor and was configuring it to 144 Hz using XRandr. It seems I messed something up and now, I can't get my monitor to work using DisplayPort. Only HDMI works.
This issue started after I typed xrandr --output DP-0 --mode 2560x1440 --rate 144.00 into terminal and moved the mouse. The screen said "no signal". I turned the monitor and computer on and off and nothing happened. Switching to HDMI fixes the problem but then I can't use the 144 Hz. I think this is a Linux related issue and not a monitor related issue since the problem started after I edited the xrandr code. The only thing I can think of is changing the xrandr setting again but I can't do that since xrandr says that DP-0 is disconnected.
I have tried:
- Changing XRandr setting
- switching out DP cables
- Clearing monitor settings file
Edit: I just noticed that when I turn my computer on with DP-0 plugged in, my monitor briefly reacts before going into standby mode. Turning it on still says "No signal".
linux ubuntu xrandr monitors resolution
asked Oct 29 '17 at 18:23
Dan
216
closed as off-topic by Jeff Schaller, Stephen Rauch, G-Man, Archemar, Anthony Geoghegan Nov 12 '17 at 22:33
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Jeff Schaller, Stephen Rauch, G-Man, Archemar, Anthony Geoghegan
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I recently got a new ViewSonic Monitor and was configuring it to 144 Hz using XRandr. It seems I messed something up and now, I can't get my monitor to work using DisplayPort. Only HDMI works.
This issue started after I typed xrandr --output DP-0 --mode 2560x1440 --rate 144.00 into terminal and moved the mouse. The screen said "no signal". I turned the monitor and computer on and off and nothing happened. Switching to HDMI fixes the problem but then I can't use the 144 Hz. I think this is a Linux related issue and not a monitor related issue since the problem started after I edited the xrandr code. The only thing I can think of is changing the xrandr setting again but I can't do that since xrandr says that DP-0 is disconnected.
I have tried:
- Changing XRandr setting
- switching out DP cables
- Clearing monitor settings file
Edit: I just noticed that when I turn my computer on with DP-0 plugged in, my monitor briefly reacts before going into standby mode. Turning it on still says "No signal".
linux ubuntu xrandr monitors resolution
asked Oct 29 '17 at 18:23
Dan
216
I recently got a new ViewSonic Monitor and was configuring it to 144 Hz using XRandr. It seems I messed something up and now, I can't get my monitor to work using DisplayPort. Only HDMI works.
This issue started after I typed xrandr --output DP-0 --mode 2560x1440 --rate 144.00 into terminal and moved the mouse. The screen said "no signal". I turned the monitor and computer on and off and nothing happened. Switching to HDMI fixes the problem but then I can't use the 144 Hz. I think this is a Linux related issue and not a monitor related issue since the problem started after I edited the xrandr code. The only thing I can think of is changing the xrandr setting again but I can't do that since xrandr says that DP-0 is disconnected.
I have tried:
- Changing XRandr setting
- switching out DP cables
- Clearing monitor settings file
Edit: I just noticed that when I turn my computer on with DP-0 plugged in, my monitor briefly reacts before going into standby mode. Turning it on still says "No signal".
linux ubuntu xrandr monitors resolution
asked Oct 29 '17 at 18:23
Dan
216
asked Oct 29 '17 at 18:23
Dan
216
asked Oct 29 '17 at 18:23
Dan
216
asked Oct 29 '17 at 18:23
Dan
216
216
closed as off-topic by Jeff Schaller, Stephen Rauch, G-Man, Archemar, Anthony Geoghegan Nov 12 '17 at 22:33
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Jeff Schaller, Stephen Rauch, G-Man, Archemar, Anthony Geoghegan
closed as off-topic by Jeff Schaller, Stephen Rauch, G-Man, Archemar, Anthony Geoghegan Nov 12 '17 at 22:33
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Jeff Schaller, Stephen Rauch, G-Man, Archemar, Anthony Geoghegan
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
I am not sure what exactly caused the issue but I solved the problem by reinstalling the nvidia driver.
edited Nov 12 '17 at 17:16
peterh
3,97092755
answered Nov 9 '17 at 19:35
Dan
216
1
You can also accept your own answers. Self-answered posts are popular things.
– peterh
Nov 12 '17 at 17:16
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
I am not sure what exactly caused the issue but I solved the problem by reinstalling the nvidia driver.
edited Nov 12 '17 at 17:16
peterh
3,97092755
answered Nov 9 '17 at 19:35
Dan
216
1
You can also accept your own answers. Self-answered posts are popular things.
– peterh
Nov 12 '17 at 17:16
add a comment |Â
up vote
1
down vote
accepted
I am not sure what exactly caused the issue but I solved the problem by reinstalling the nvidia driver.
edited Nov 12 '17 at 17:16
peterh
3,97092755
answered Nov 9 '17 at 19:35
Dan
216
1
You can also accept your own answers. Self-answered posts are popular things.
– peterh
Nov 12 '17 at 17:16
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
I am not sure what exactly caused the issue but I solved the problem by reinstalling the nvidia driver.
edited Nov 12 '17 at 17:16
peterh
3,97092755
answered Nov 9 '17 at 19:35
Dan
216
I am not sure what exactly caused the issue but I solved the problem by reinstalling the nvidia driver.
edited Nov 12 '17 at 17:16
peterh
3,97092755
answered Nov 9 '17 at 19:35
Dan
216
edited Nov 12 '17 at 17:16
peterh
3,97092755
edited Nov 12 '17 at 17:16
peterh
3,97092755
edited Nov 12 '17 at 17:16
peterh
3,97092755
3,97092755
answered Nov 9 '17 at 19:35
Dan
216
answered Nov 9 '17 at 19:35
Dan
216
answered Nov 9 '17 at 19:35
Dan
216
216
1
You can also accept your own answers. Self-answered posts are popular things.
– peterh
Nov 12 '17 at 17:16
add a comment |Â
1
You can also accept your own answers. Self-answered posts are popular things.
– peterh
Nov 12 '17 at 17:16
1
1
You can also accept your own answers. Self-answered posts are popular things.
– peterh
Nov 12 '17 at 17:16
You can also accept your own answers. Self-answered posts are popular things.
– peterh
Nov 12 '17 at 17:16
add a comment |Â