Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #161374 > unrolled thread

Upgrade to Jessie lost all monitor resolutions except 1024x768

Started byMarc Shapiro <marcnshap@gmail.com>
First post2015-11-30 22:30 +0100
Last post2015-12-01 01:20 +0100
Articles 6 — 4 participants

Back to article view | Back to linux.debian.user


Contents

  Upgrade to Jessie lost all monitor resolutions except 1024x768 Marc Shapiro <marcnshap@gmail.com> - 2015-11-30 22:30 +0100
    Re: Upgrade to Jessie lost all monitor resolutions except 1024x768 Marc Shapiro <marcnshap@gmail.com> - 2015-11-30 23:30 +0100
      Re: Upgrade to Jessie lost all monitor resolutions except 1024x768 Ansgar Burchardt <"Ansgar Burchardt"@43-1.org> - 2015-11-30 23:40 +0100
        Re: Upgrade to Jessie lost all monitor resolutions except 1024x768 Marc Shapiro <marcnshap@gmail.com> - 2015-12-01 00:10 +0100
          Re: Upgrade to Jessie lost all monitor resolutions except 1024x768 Felix Miata <mrmazda@earthlink.net> - 2015-12-01 01:00 +0100
    Re: Upgrade to Jessie lost all monitor resolutions except 1024x768 Mike Kupfer <m.kupfer@acm.org> - 2015-12-01 01:20 +0100

#161374 — Upgrade to Jessie lost all monitor resolutions except 1024x768

FromMarc Shapiro <marcnshap@gmail.com>
Date2015-11-30 22:30 +0100
SubjectUpgrade to Jessie lost all monitor resolutions except 1024x768
Message-ID<qAEbg-uO-37@gated-at.bofh.it>
I have been holding off on upgrading to Jessie, but I decided that it 
was time to at least try it out.

I made a copy of my current system in unused space on my disk and 
updated lilo.  After verifying that I could boot into both setups, I 
upgraded the copy to Jessie after installing sysvinit-core to avoid 
systemd.  It boots and lets me log in on multiple consoles as different 
users.  Each user can run startx and gets their own session on separate 
vts specific to the user.  This was my big question, and it seems to 
work fine.  (We'll have to see about Jessie+1, it seems.)

My problem now is screen resolution.  All I get is 1024x768.  Under 
Wheezy I get 15 different resolutions from 720x400 and 640x480 up to 
1920x1080.  Jessie says that the monitor is "Unknown" and only allows me 
to use 1024x768.  How do I get X to recognize my monitor under Jessie?

Marc

[toc] | [next] | [standalone]


#161376

FromMarc Shapiro <marcnshap@gmail.com>
Date2015-11-30 23:30 +0100
Message-ID<qAF7k-15b-15@gated-at.bofh.it>
In reply to#161374
On 11/30/2015 01:21 PM, Marc Shapiro wrote:
> I have been holding off on upgrading to Jessie, but I decided that it 
> was time to at least try it out.
>
> I made a copy of my current system in unused space on my disk and 
> updated lilo.  After verifying that I could boot into both setups, I 
> upgraded the copy to Jessie after installing sysvinit-core to avoid 
> systemd.  It boots and lets me log in on multiple consoles as 
> different users.  Each user can run startx and gets their own session 
> on separate vts specific to the user.  This was my big question, and 
> it seems to work fine.  (We'll have to see about Jessie+1, it seems.)
>
> My problem now is screen resolution.  All I get is 1024x768. Under 
> Wheezy I get 15 different resolutions from 720x400 and 640x480 up to 
> 1920x1080.  Jessie says that the monitor is "Unknown" and only allows 
> me to use 1024x768.  How do I get X to recognize my monitor under Jessie?
>
> Marc

I decided, since this was just a test, to install systemd-sysv (which 
should remove sysvinit-core) so that I could see if booting with systemd 
would make a difference.   But...

I can't install systemd-sysv.  I get the following:

# aptitude install systemd-sysv
No candidate version found for systemd-sysv
No candidate version found for systemd-sysv
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.

and:

# aptitude show systemd-sysv
No current or candidate version found for systemd-sysv
Package: systemd-sysv
New: yes
State: not installed
Version: 215-17+deb8u2
Priority: important
Section: admin
Maintainer: Debian systemd Maintainers 
<pkg-systemd-maintainers@lists.alioth.debian.org>
Architecture: amd64
Uncompressed Size: 78.8 k
Depends: systemd (= 215-17+deb8u2)
PreDepends: systemd
Conflicts: sysvinit-core, sysvinit-core, upstart, upstart, systemd-sysv
Replaces: sysvinit (< 2.88dsf-44~), sysvinit (< 2.88dsf-44~), 
sysvinit-core, sysvinit-core, upstart, upstart
Description: system and service manager - SysV links
  systemd is a replacement for sysvinit.  It is dependency-based and 
able to read the LSB init script headers in addition to
  parsing rcN.d links as hints.

  It also provides process supervision using cgroups and the ability to 
not only depend on other init script being started,
  but also availability of a given mount point or dbus service.

  This package provides the manual pages and links needed for systemd to 
replace sysvinit. Installing systemd-sysv will
  overwrite /sbin/init with a link to systemd.
Homepage: http://www.freedesktop.org/wiki/Software/systemd

which suggests that it exists, but nothing is installable.  Now, I would 
be happier to get this working without systemd, but shouldn't systemd be 
installable?

Marc

[toc] | [prev] | [next] | [standalone]


#161378

FromAnsgar Burchardt <"Ansgar Burchardt"@43-1.org>
Date2015-11-30 23:40 +0100
Message-ID<qAFh0-18d-11@gated-at.bofh.it>
In reply to#161376
Marc Shapiro <marcnshap@gmail.com> writes:
> I decided, since this was just a test, to install systemd-sysv (which
> should remove sysvinit-core) so that I could see if booting with
> systemd would make a difference.   But...
>
> I can't install systemd-sysv.  I get the following:
[...]
> which suggests that it exists, but nothing is installable.  Now, I
> would be happier to get this working without systemd, but shouldn't
> systemd be installable?

Did you maybe pin systemd-sysv to make sure it didn't get installed?
Check /etc/apt/preferences & /etc/apt/preferences.d or the output of
"apt-cache policy systemd-sysv".

If you try systemd, you might want to make sure that "sysvinit" is
installed. This should provide an entry in grub's boot menu to start
with sysvinit in case anything goes wrong; with other bootloaders one
can pass init=/lib/sysvinit/init to do so.

Though it would surprise me a bit if this affects X in Jessie.

Ansgar

[toc] | [prev] | [next] | [standalone]


#161379

FromMarc Shapiro <marcnshap@gmail.com>
Date2015-12-01 00:10 +0100
Message-ID<qAFK1-1An-7@gated-at.bofh.it>
In reply to#161378
On 11/30/2015 02:36 PM, Ansgar Burchardt wrote:
> Marc Shapiro <marcnshap@gmail.com> writes:
>> I decided, since this was just a test, to install systemd-sysv (which
>> should remove sysvinit-core) so that I could see if booting with
>> systemd would make a difference.   But...
>>
>> I can't install systemd-sysv.  I get the following:
> [...]
>> which suggests that it exists, but nothing is installable.  Now, I
>> would be happier to get this working without systemd, but shouldn't
>> systemd be installable?
> Did you maybe pin systemd-sysv to make sure it didn't get installed?
> Check /etc/apt/preferences & /etc/apt/preferences.d or the output of
> "apt-cache policy systemd-sysv".
>
> If you try systemd, you might want to make sure that "sysvinit" is
> installed. This should provide an entry in grub's boot menu to start
> with sysvinit in case anything goes wrong; with other bootloaders one
> can pass init=/lib/sysvinit/init to do so.
>
> Though it would surprise me a bit if this affects X in Jessie.
>
> Ansgar
>
Yes.  That was the reason that I could not install systemd-sysv.  I had 
forgotten having done that.  I eliminated the pin and installed 
systemd-sysv.  Then I rebooted.  Unfortunately, it did not solve the 
problem.  The monitor is still "Unknown" and only 1024x768 resolution is 
available.

Marc

[toc] | [prev] | [next] | [standalone]


#161384

FromFelix Miata <mrmazda@earthlink.net>
Date2015-12-01 01:00 +0100
Message-ID<qAGwq-1UV-15@gated-at.bofh.it>
In reply to#161379
Marc Shapiro composed on 2015-11-30 15:01 (UTC-0800):

> The monitor is still "Unknown" and only 1024x768 resolution is available.

Whenever anyone needs help with Xorg, he should share hardware info and
Xorg.0.log. X troubleshooting is heavily dependent on specific gfxchip. In
your case, provide both pre-Jessie and Jessie logs (unwrapped, e.g.
http://paste.debian.net/ or your own personal web space) so we can compare.
Maybe the driver for your gfxchip has been retired and you're using an
unaccelerated and limited function fallback driver limited to 1024x768 (e.g.
VESA). Automagic X configuration may need an override for your gfxchip.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]


#161387

FromMike Kupfer <m.kupfer@acm.org>
Date2015-12-01 01:20 +0100
Message-ID<qAGG5-2ec-11@gated-at.bofh.it>
In reply to#161374
Marc Shapiro wrote:

> My problem now is screen resolution.  All I get is 1024x768.  Under
> Wheezy I get 15 different resolutions from 720x400 and 640x480 up to
> 1920x1080.  Jessie says that the monitor is "Unknown" and only allows
> me to use 1024x768.  How do I get X to recognize my monitor under
> Jessie?

Here are a couple troubleshooting steps that I would try:

- Check for a legacy configuration file (e.g., /etc/X11/xorg.conf).  If
  one is present, try moving it out of the way and restarting X.

- Boot a Live image and see what resolution it gives you.

HTH,
mike

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web