Display issues on Debian Buster
by pompopom from LinuxQuestions.org on (#535DH)
Hi everyone,
First post here.
Not exactly a newbie in linux, but I'll never call myself a specialist or guru. I usually work on machines without GUI. So... ok let's go.
I'm installing a "new" PC in my electronics lab. In fact it's the previous PC of my better half, but should be more than sufficient to run the tools I want to run.
Hardware:Code:Asus Motherboard, Intel Core DUO. 6GB RAM
Matrox G550 dual DVI from which only one is connected to an Acer B193W monitor.
OS Debian - GNOME
I have 2 x 1TB disks partitioned in software RAID. Some partitions in RAID-0 others in RAID-1History:
I originally always installed Debian Stretch and did an upgrade to Buster afterwards. Just because I had the DVD laying around and was to lazy to burn a new install CD. Stretch installation went smooth but after upgrade to Buster, screen resolution fell back to 640x800 with no way to increase resolution (xrandr only showed this as option also...)
I admit I didn't invest to much time, so after two attempts and some fiddling I burnt an install CD for Buster directly.
Again installation itself is smooth, no probs here, but then the issues began...
After first reboot, I get the GRUB menu in high resolution and booting continues. Soon after that screen turns black and shows me "input not supported" After some troubleshooting (rebooting, switching videocard from MB slot, using other cables, convert DVI to VGA to use other input on monitor, ...) I came to the conclusioin that after each reboot I get the issue.
Solution: unplug the DVI, wait a few sec, replug: Login window appears (in correct resolution). I can call this a work-around, but it's not really handy.
2nd problem: When the OS goes into suspend (both automatically as manual) I'm not able to have the monitor resurrect. Machine starts but in no way I'm getting video on the monitor (not even with the above workaround after boot) I've been Googling a lot and it seems this has happened in the past already, but despite all the "solutions" posted I had no luck.
I'm not sure if both are related. But I might as well mention it.
Hope that this rings a bell with someone somewhere...
Sorry for the long post.
regards.
First post here.
Not exactly a newbie in linux, but I'll never call myself a specialist or guru. I usually work on machines without GUI. So... ok let's go.
I'm installing a "new" PC in my electronics lab. In fact it's the previous PC of my better half, but should be more than sufficient to run the tools I want to run.
Hardware:Code:Asus Motherboard, Intel Core DUO. 6GB RAM
Matrox G550 dual DVI from which only one is connected to an Acer B193W monitor.
OS Debian - GNOME
I have 2 x 1TB disks partitioned in software RAID. Some partitions in RAID-0 others in RAID-1History:
I originally always installed Debian Stretch and did an upgrade to Buster afterwards. Just because I had the DVD laying around and was to lazy to burn a new install CD. Stretch installation went smooth but after upgrade to Buster, screen resolution fell back to 640x800 with no way to increase resolution (xrandr only showed this as option also...)
I admit I didn't invest to much time, so after two attempts and some fiddling I burnt an install CD for Buster directly.
Again installation itself is smooth, no probs here, but then the issues began...
After first reboot, I get the GRUB menu in high resolution and booting continues. Soon after that screen turns black and shows me "input not supported" After some troubleshooting (rebooting, switching videocard from MB slot, using other cables, convert DVI to VGA to use other input on monitor, ...) I came to the conclusioin that after each reboot I get the issue.
Solution: unplug the DVI, wait a few sec, replug: Login window appears (in correct resolution). I can call this a work-around, but it's not really handy.
2nd problem: When the OS goes into suspend (both automatically as manual) I'm not able to have the monitor resurrect. Machine starts but in no way I'm getting video on the monitor (not even with the above workaround after boot) I've been Googling a lot and it seems this has happened in the past already, but despite all the "solutions" posted I had no luck.
I'm not sure if both are related. But I might as well mention it.
Hope that this rings a bell with someone somewhere...
Sorry for the long post.
regards.