kernel-packages team mailing list archive

[Johnny Rogers <jrogers@xxxxxxxxx>]

Well since I reported this here, I had gotten a GeForce 210 graphics
card, and had installed another Linux Distro (Opensuse Leap). But
currently I'm in process of deciding which linux distro I'll stick with,
I just dban'd the drive last night while I slept. Initially when I
reported this bug, I didn't have a graphics card installed nor nvidia
drivers, was just using VGA to VGA cable.

I believe what happened though, was that I had swapped towers out,
putting the main tower that Kubuntu Wily was being installed on, with
monitor that has max resolution of 1024x768. Then once installation was
done, I unplugged the tower, and put it back over here and hooked it up
with the 24" tower, and then after some updates, the resolution kicked
out for 1920x1200 to 1024x768. Since Kubuntu Wily was originally
installed using 1024x768 monitor and not the 1920x1200 monitor. Hence
the 1920x1200 sticking properly.

Another possibility is that this monitor was given to me free by friend
and apparently it had mild water damage to circuit board where the plug
ports are in back of monitor for VGA, HDMI, DVI-D etc. I had cleaned
those up of course and circuit board, something has been quirky when
using the DVI-D single slot (in back of monitor) to HDMI cable, with
HDMI plug to graphic card. Makes the screen go black, and back on,
black, and back on, black, and back on repeatedly several times, and
then finally sticks / registers itself .. This is in OpenSuse Leap.

But using VGA to VGA (all one input / output source) from monitor to
graphic card, it doesn't behave like that. I ordered a HDMI to HDMI
cable once and waiting for that to come in mail then and see if that
will work and give better display than the VGA to VGA cable. I had
installed Kubuntu Wily few times since I got graphic card and it's nice
that Kubuntu Wily automatically detects the card and provides right
NVIDIA drivers for card, where OpenSuse Leap doesn't. With Leap, I have
to add NVIDIA repository and then do "zypper dup" to get the drivers, or
install them manually.

At this point, I'll probably go with Kubuntu Wily though, because it's
more familiar to me and less complex and less buggy compared to OpenSuse
13.2, Leap 42.1, and Tumbleweed. Regarding this bug here, I'm not sure
what to say or do about it now, since I've gotten the graphics card to
act like a "middleman" between a more modern monitor and my older
chipset Dell Optiplex 755. Because several times before, if I left tower
hooked to 24" monitor and installed Kubuntu Wily,  the screen resolution
usually stays and doesn't change.

What do you suggest? Remove graphic card, reinstall Wily, and see if it
happens again? Or just keep graphics card installed (I'll need it
installed anyway though, to hook up the HDMI to HDMI cable in near
future, because tower don't have HDMI port in back of it, only VGA
port), install Wily, and see if any issues come up?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1496662

Title:
  Latest update affects 1920x1200 screen resolution, max size 1024x768
  only.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I updated Kubuntu Wily via system updater in lower taskbar area, and
  after installing the packages it said to reboot computer in order for
  it take affect. I rebooted, and once rebooted to screen to enter
  encryption password / LVM, the resolution was changed. I went into
  System Settings > Monitor/Display and it only allows me to go to
  maximum resolution of 1024x768. Before this update, it was fine, no
  display issues. 1920x1200. 24" NEC AccuSync LCD WMCX monitor. If you
  need more specs for computer let me know.

  One of these I believe, because after I did it via updater from task
  bar, it prompted me to reboot. I did do some updates via terminal
  before this, and didn't lose resolution.

  Start-Date: 2015-09-16  20:34:46
  Install: linux-headers-4.2.0-10-generic:amd64 (4.2.0-10.11, automatic), linux-headers-4.2.0-10:amd64 (4.2.0-10.11, automatic), linux-image-extra-4.2.0-10-generic:amd64 (4.2.0-10.11, automatic), linux-image-4.2.0-10-generic:amd64 (4.2.0-10.11, automatic)
  Upgrade: linux-headers-generic:amd64 (4.2.0.7.7, 4.2.0.10.10), linux-image-generic:amd64 (4.2.0.7.7, 4.2.0.10.10), linux-generic:amd64 (4.2.0.7.7, 4.2.0.10.10)
  End-Date: 2015-09-16  20:35:59

  Update/upgrade from terminal was the following:

  Start-Date: 2015-09-16  19:50:28
  Commandline: apt-get upgrade
  Upgrade: thunderbird-locale-en-us:amd64 (31.8.0+build1-0ubuntu1, 38.2.0+build1-0ubuntu3), thunderbird:amd64 (31.8.0+build1-0ubuntu1, 38.2.0+build1-0ubuntu3), libpython3.5:amd64 (3.5.0-1, 3.5.0-1ubuntu1), libldap-2.4-2:amd64 (2.4.41+dfsg-1ubuntu1, 2.4.41+dfsg-1ubuntu2), thunderbird-locale-en:amd64 (31.8.0+build1-0ubuntu1, 38.2.0+build1-0ubuntu3), libpython3.5-stdlib:amd64 (3.5.0-1, 3.5.0-1ubuntu1), kbd:amd64 (1.15.5-1ubuntu3, 1.15.5-1ubuntu4), gnome-icon-theme:amd64 (3.12.0-1ubuntu1, 3.12.0-1ubuntu2), libpython3.5-minimal:amd64 (3.5.0-1, 3.5.0-1ubuntu1)
  End-Date: 2015-09-16  19:50:46

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496662/+subscriptions