Upgrade to Jessie lost all monitor resolutions except 1024x768

classic Classic list List threaded Threaded
30 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Upgrade to Jessie lost all monitor resolutions except 1024x768

Marc Shapiro-3
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

Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

Marc Shapiro-3
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
<[hidden email]>
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

Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

Ansgar Burchardt-9
Marc Shapiro <[hidden email]> 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

Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

Marc Shapiro-3
On 11/30/2015 02:36 PM, Ansgar Burchardt wrote:

> Marc Shapiro <[hidden email]> 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

Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

Felix Miata-3
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/

Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

Mike Kupfer
In reply to this post by Marc Shapiro-3
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

Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

Marc Shapiro-3
On 11/30/2015 04:01 PM, Mike Kupfer wrote:

> 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.
Does not exist.  That was the first thing I looked for.
> - Boot a Live image and see what resolution it gives you.
I can still boot into Wheezy and get 1920x1080.

Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

Mike Kupfer
Marc Shapiro wrote:

> On 11/30/2015 04:01 PM, Mike Kupfer wrote:
> > - Boot a Live image and see what resolution it gives you.
> I can still boot into Wheezy and get 1920x1080.

I meant a Jessie Live image.

Though given that you didn't find an old xorg.conf file, the odds of the
Live image doing something different seem pretty slim.

I agree with Felix's recommendation to post information about the
graphics card and at least the Jessie X log file (having both the Jessie
and Wheezy log files would be better).

regards,
mike

Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

Marc Shapiro-3
On 11/30/2015 04:45 PM, Mike Kupfer wrote:

> Marc Shapiro wrote:
>
>> On 11/30/2015 04:01 PM, Mike Kupfer wrote:
>>> - Boot a Live image and see what resolution it gives you.
>> I can still boot into Wheezy and get 1920x1080.
> I meant a Jessie Live image.
>
> Though given that you didn't find an old xorg.conf file, the odds of the
> Live image doing something different seem pretty slim.
>
> I agree with Felix's recommendation to post information about the
> graphics card and at least the Jessie X log file (having both the Jessie
> and Wheezy log files would be better).
>
> regards,
> mike
I have a copy of Xorg.0.log for both Wheezy and Jessie.  How do I post
them to paste.debian.net?

Marc

Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

Lisi Reisz
On Tuesday 01 December 2015 01:10:33 Marc Shapiro wrote:

> On 11/30/2015 04:45 PM, Mike Kupfer wrote:
> > Marc Shapiro wrote:
> >> On 11/30/2015 04:01 PM, Mike Kupfer wrote:
> >>> - Boot a Live image and see what resolution it gives you.
> >>
> >> I can still boot into Wheezy and get 1920x1080.
> >
> > I meant a Jessie Live image.
> >
> > Though given that you didn't find an old xorg.conf file, the odds of the
> > Live image doing something different seem pretty slim.
> >
> > I agree with Felix's recommendation to post information about the
> > graphics card and at least the Jessie X log file (having both the Jessie
> > and Wheezy log files would be better).
> >
> > regards,
> > mike
>
> I have a copy of Xorg.0.log for both Wheezy and Jessie.  How do I post
> them to paste.debian.net?
>
> Marc

Just send them here so that all of us and the archives can see them.

Lisi

Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

Mike Kupfer
In reply to this post by Marc Shapiro-3
Marc Shapiro wrote:

> I have a copy of Xorg.0.log for both Wheezy and Jessie.  How do I post
> them to paste.debian.net?

Well, I don't have a preference as far as using paste.debian.net or
posting straight to the list.  To use paste.debian.net, start a browser
and go to http://paste.debian.net/.  Click on Browse, select the file,
add a note to indicate which log file it is (if it's not obvious), click
on Send.

regards,
mike

Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

Mike Kupfer
Mike Kupfer wrote:

> To use paste.debian.net, start a browser
> and go to http://paste.debian.net/.  Click on Browse, select the file,
> add a note to indicate which log file it is (if it's not obvious), click
> on Send.

Oops, forgot to mention: that should take you to a new page that
contains the log file.  Send the URLs to the list.

regards,
mike

Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

Marc Shapiro-3
In reply to this post by Lisi Reisz
On 11/30/2015 05:27 PM, Marc Shapiro wrote:

> On 11/30/2015 05:24 PM, Lisi Reisz wrote:
>> On Tuesday 01 December 2015 01:10:33 Marc Shapiro wrote:
>>> On 11/30/2015 04:45 PM, Mike Kupfer wrote:
>>>> Marc Shapiro wrote:
>>>>> On 11/30/2015 04:01 PM, Mike Kupfer wrote:
>>>>>> - Boot a Live image and see what resolution it gives you.
>>>>> I can still boot into Wheezy and get 1920x1080.
>>>> I meant a Jessie Live image.
>>>>
>>>> Though given that you didn't find an old xorg.conf file, the odds
>>>> of the
>>>> Live image doing something different seem pretty slim.
>>>>
>>>> I agree with Felix's recommendation to post information about the
>>>> graphics card and at least the Jessie X log file (having both the
>>>> Jessie
>>>> and Wheezy log files would be better).
>>>>
>>>> regards,
>>>> mike
>>> I have a copy of Xorg.0.log for both Wheezy and Jessie.  How do I post
>>> them to paste.debian.net?
>>>
>>> Marc
>> Just send them here so that all of us and the archives can see them.
>>
>> Lisi
>>
> OK.  Here they are.  I hope someone can make better sense of them than
> I can.  Log files are not my friend.
>
> Marc
Alright.  Knowing nothing about the inner workings of X, I can at least
look through the two log files (in my previous post) and see where they
suddenly go in very different directions.

Using the numbers down the left-hand side of the logs (I don't know what
they actually are, but they seem to be ascending, so I will use them as
markers), at 32.959 in the Wheezy log and at 2271.289 in the Jessie log
they both say:

     (++) using VT number 7

a few lines below that, in the Wheezy log:


[    32.974] (II) Module fbdevhw: vendor="X.Org Foundation"
[    32.974]    compiled for 1.12.4, module version = 0.0.2
[    32.974]    ABI class: X.Org Video Driver, version 12.1
[    32.975] (II) RADEON(0): TOTO SAYS 00000000fddc0000
[    32.975] (II) RADEON(0): MMIO registers at 0x00000000fddc0000: size
128KB
[    32.975] (II) RADEON(0): PCI bus 1 card 0 func 0
[    32.975] (II) RADEON(0): Creating default Display subsection in
Screen section
         "Default Screen Section" for depth/fbbpp 24/32
[    32.975] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
[    32.975] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32
bpp pixmaps)
[    32.975] (==) RADEON(0): Default visual is TrueColor

     SKIP

[    33.024] (II) RADEON(0): Detected total video RAM=1048576K,
accessible=262144K (PCI BAR=262144K)

and in the Jessie log:

[  2271.291] (II) Module fbdevhw: vendor="X.Org Foundation"
[  2271.291]    compiled for 1.16.4, module version = 0.0.2
[  2271.291]    ABI class: X.Org Video Driver, version 18.0
[  2271.291] (**) FBDEV(2): claimed PCI slot 1@0:0:0
[  2271.291] (II) FBDEV(2): using default device
[  2271.291] (WW) Falling back to old probe method for vesa
[  2271.291] (EE) Screen 0 deleted because of no matching config section.
[  2271.291] (II) UnloadModule: "radeon"
[  2271.291] (EE) Screen 0 deleted because of no matching config section.
[  2271.291] (II) UnloadModule: "modesetting"
[  2271.291] (II) FBDEV(0): Creating default Display subsection in
Screen section
         "Default Screen Section" for depth/fbbpp 16/16
[  2271.291] (==) FBDEV(0): Depth 16, (==) framebuffer bpp 16
[  2271.291] (==) FBDEV(0): RGB weight 565
[  2271.291] (==) FBDEV(0): Default visual is TrueColor
[  2271.291] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[  2271.291] (II) FBDEV(0): hardware: simple (video memory: 1536kB)
[  2271.291] (II) FBDEV(0): checking modes against framebuffer device...
[  2271.291] (II) FBDEV(0): checking modes against monitor...
[  2271.291] (--) FBDEV(0): Virtual size is 1024x768 (pitch 1024)
[  2271.291] (**) FBDEV(0):  Built-in mode "current"
[  2271.291] (==) FBDEV(0): DPI set to (96, 96)


In Wheezy, the graphics card seems to have been found and a depth of
24bpp is being used by RADEON(0) with a GB of graphics memory, while in
Jessie, Screen 0 is getting deleted and the radeon module is removed.  
Instead of RADEON(0) we see FBDEV(0), instead of 24bbp, only 16bbp is
being used.  Only 1536kB of video memory is being used and the screen
size is set to "Virtual size is 1024x768 (pitch 1024)".

I don't know enough to determine what is causing these differences, let
alone how to correct the problem.  If someone else can figure out a
solution I would be most grateful.

Marc

Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

Felix Miata-3
Marc Shapiro composed on 2015-11-30 23:11 (UTC-0800):

> Alright.  Knowing nothing about the inner workings of X, I can at least
> look through the two log files (in my previous post) and see where they
> suddenly go in very different directions.

> Using the numbers down the left-hand side of the logs (I don't know what
> they actually are, but they seem to be ascending, so I will use them as
> markers), at 32.959 in the Wheezy log and at 2271.289 in the Jessie log
> they both say:

>      (++) using VT number 7

> a few lines below that, in the Wheezy log:

> [    32.974] (II) Module fbdevhw: vendor="X.Org Foundation"
> [    32.974]    compiled for 1.12.4, module version = 0.0.2
> [    32.974]    ABI class: X.Org Video Driver, version 12.1
> [    32.975] (II) RADEON(0): TOTO SAYS 00000000fddc0000
> [    32.975] (II) RADEON(0): MMIO registers at 0x00000000fddc0000: size  128KB
> [    32.975] (II) RADEON(0): PCI bus 1 card 0 func 0
> [    32.975] (II) RADEON(0): Creating default Display subsection in Screen section
>          "Default Screen Section" for depth/fbbpp 24/32
> [    32.975] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
> [    32.975] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
> [    32.975] (==) RADEON(0): Default visual is TrueColor

>      SKIP

> [    33.024] (II) RADEON(0): Detected total video RAM=1048576K, accessible=262144K (PCI BAR=262144K)

> and in the Jessie log:

> [  2271.291] (II) Module fbdevhw: vendor="X.Org Foundation"
> [  2271.291]    compiled for 1.16.4, module version = 0.0.2
> [  2271.291]    ABI class: X.Org Video Driver, version 18.0
> [  2271.291] (**) FBDEV(2): claimed PCI slot 1@0:0:0
> [  2271.291] (II) FBDEV(2): using default device
> [  2271.291] (WW) Falling back to old probe method for vesa
> [  2271.291] (EE) Screen 0 deleted because of no matching config section.
> [  2271.291] (II) UnloadModule: "radeon"
> [  2271.291] (EE) Screen 0 deleted because of no matching config section.
> [  2271.291] (II) UnloadModule: "modesetting"
> [  2271.291] (II) FBDEV(0): Creating default Display subsection in Screen section
>          "Default Screen Section" for depth/fbbpp 16/16
> [  2271.291] (==) FBDEV(0): Depth 16, (==) framebuffer bpp 16
> [  2271.291] (==) FBDEV(0): RGB weight 565
> [  2271.291] (==) FBDEV(0): Default visual is TrueColor
> [  2271.291] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
> [  2271.291] (II) FBDEV(0): hardware: simple (video memory: 1536kB)
> [  2271.291] (II) FBDEV(0): checking modes against framebuffer device...
> [  2271.291] (II) FBDEV(0): checking modes against monitor...
> [  2271.291] (--) FBDEV(0): Virtual size is 1024x768 (pitch 1024)
> [  2271.291] (**) FBDEV(0):  Built-in mode "current"
> [  2271.291] (==) FBDEV(0): DPI set to (96, 96)

> In Wheezy, the graphics card seems to have been found and a depth of
> 24bpp is being used by RADEON(0) with a GB of graphics memory, while in
> Jessie, Screen 0 is getting deleted and the radeon module is removed.  
> Instead of RADEON(0) we see FBDEV(0), instead of 24bbp, only 16bbp is
> being used.  Only 1536kB of video memory is being used and the screen
> size is set to "Virtual size is 1024x768 (pitch 1024)".

FBDEV doesn't ever support 1920x1080 AFAIK. Video RAM and bpp are non-issues
here. What needs to be determined is why RADEON is not being used in Jessie.
FBDEV is a grossly inferior fallback.

> I don't know enough to determine what is causing these differences, let
> alone how to correct the problem.  If someone else can figure out a
> solution I would be most grateful.

You haven't provided everything requested. We don't know which gfxcard you
have, which 'lspci | grep VGA' would report. Your excerpts from Xorg.0.logs
don't have other info that may be required to help, such as kernel cmdline,
which could be the reason why RADEON is not used. Another possibility is that
Jessie provides firmware your ATI gfxcard requires in a separate firmware
package that is not installed, or maybe the ATI driver package didn't get
installed at all. Read through
https://wiki.debian.org/AtiHowTo#Troubleshooting and you may not need any
more help from us.
--
"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/

Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

Marc Shapiro-3
On 11/30/2015 11:32 PM, Felix Miata wrote:

> Marc Shapiro composed on 2015-11-30 23:11 (UTC-0800):
>
>> Alright.  Knowing nothing about the inner workings of X, I can at least
>> look through the two log files (in my previous post) and see where they
>> suddenly go in very different directions.
>> Using the numbers down the left-hand side of the logs (I don't know what
>> they actually are, but they seem to be ascending, so I will use them as
>> markers), at 32.959 in the Wheezy log and at 2271.289 in the Jessie log
>> they both say:
>>       (++) using VT number 7
>> a few lines below that, in the Wheezy log:
>> [    32.974] (II) Module fbdevhw: vendor="X.Org Foundation"
>> [    32.974]    compiled for 1.12.4, module version = 0.0.2
>> [    32.974]    ABI class: X.Org Video Driver, version 12.1
>> [    32.975] (II) RADEON(0): TOTO SAYS 00000000fddc0000
>> [    32.975] (II) RADEON(0): MMIO registers at 0x00000000fddc0000: size  128KB
>> [    32.975] (II) RADEON(0): PCI bus 1 card 0 func 0
>> [    32.975] (II) RADEON(0): Creating default Display subsection in Screen section
>>           "Default Screen Section" for depth/fbbpp 24/32
>> [    32.975] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
>> [    32.975] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
>> [    32.975] (==) RADEON(0): Default visual is TrueColor
>>       SKIP
>> [    33.024] (II) RADEON(0): Detected total video RAM=1048576K, accessible=262144K (PCI BAR=262144K)
>> and in the Jessie log:
>> [  2271.291] (II) Module fbdevhw: vendor="X.Org Foundation"
>> [  2271.291]    compiled for 1.16.4, module version = 0.0.2
>> [  2271.291]    ABI class: X.Org Video Driver, version 18.0
>> [  2271.291] (**) FBDEV(2): claimed PCI slot 1@0:0:0
>> [  2271.291] (II) FBDEV(2): using default device
>> [  2271.291] (WW) Falling back to old probe method for vesa
>> [  2271.291] (EE) Screen 0 deleted because of no matching config section.
>> [  2271.291] (II) UnloadModule: "radeon"
>> [  2271.291] (EE) Screen 0 deleted because of no matching config section.
>> [  2271.291] (II) UnloadModule: "modesetting"
>> [  2271.291] (II) FBDEV(0): Creating default Display subsection in Screen section
>>           "Default Screen Section" for depth/fbbpp 16/16
>> [  2271.291] (==) FBDEV(0): Depth 16, (==) framebuffer bpp 16
>> [  2271.291] (==) FBDEV(0): RGB weight 565
>> [  2271.291] (==) FBDEV(0): Default visual is TrueColor
>> [  2271.291] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
>> [  2271.291] (II) FBDEV(0): hardware: simple (video memory: 1536kB)
>> [  2271.291] (II) FBDEV(0): checking modes against framebuffer device...
>> [  2271.291] (II) FBDEV(0): checking modes against monitor...
>> [  2271.291] (--) FBDEV(0): Virtual size is 1024x768 (pitch 1024)
>> [  2271.291] (**) FBDEV(0):  Built-in mode "current"
>> [  2271.291] (==) FBDEV(0): DPI set to (96, 96)
>> In Wheezy, the graphics card seems to have been found and a depth of
>> 24bpp is being used by RADEON(0) with a GB of graphics memory, while in
>> Jessie, Screen 0 is getting deleted and the radeon module is removed.
>> Instead of RADEON(0) we see FBDEV(0), instead of 24bbp, only 16bbp is
>> being used.  Only 1536kB of video memory is being used and the screen
>> size is set to "Virtual size is 1024x768 (pitch 1024)".
> FBDEV doesn't ever support 1920x1080 AFAIK. Video RAM and bpp are non-issues
> here. What needs to be determined is why RADEON is not being used in Jessie.
> FBDEV is a grossly inferior fallback.
>
>> I don't know enough to determine what is causing these differences, let
>> alone how to correct the problem.  If someone else can figure out a
>> solution I would be most grateful.
> You haven't provided everything requested. We don't know which gfxcard you
> have, which 'lspci | grep VGA' would report. Your excerpts from Xorg.0.logs
> don't have other info that may be required to help, such as kernel cmdline,
> which could be the reason why RADEON is not used. Another possibility is that
> Jessie provides firmware your ATI gfxcard requires in a separate firmware
> package that is not installed, or maybe the ATI driver package didn't get
> installed at all. Read through
> https://wiki.debian.org/AtiHowTo#Troubleshooting and you may not need any
> more help from us.

Here is the lspci output showing the graphics card:

$ lspci | grep VGA
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
Cedar PRO [Radeon HD 5450/6350]

My post prior to the one you quoted above has the entire contents of
both logs.  After posting them, I saw where the logs diverged so
radically and made another post with just the excerpts.

Marc

Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

Mart van de Wege
In reply to this post by Felix Miata-3
Felix Miata <[hidden email]> writes:

> Another possibility is that Jessie provides firmware your ATI gfxcard
> requires in a separate firmware package that is not installed, or
> maybe the ATI driver package didn't get installed at all.

I manage a bunch of workstations with exactly this issue. I had to
install firmware-linux-nonfree to get X to recognise the Radeon cards in
these machines. Since firmware-linux-nonfree pulls in
firmware-amd-graphics, I suspect installing the latter will be
sufficient for OP.

Mart

--
"We will need a longer wall when the revolution comes."
    --- AJS, quoting an uncertain source.

Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

cbannister
In reply to this post by Marc Shapiro-3
On Mon, Nov 30, 2015 at 05:10:33PM -0800, Marc Shapiro wrote:

> On 11/30/2015 04:45 PM, Mike Kupfer wrote:
> >Marc Shapiro wrote:
> >
> >>On 11/30/2015 04:01 PM, Mike Kupfer wrote:
> >>>- Boot a Live image and see what resolution it gives you.
> >>I can still boot into Wheezy and get 1920x1080.
> >I meant a Jessie Live image.
> >
> >Though given that you didn't find an old xorg.conf file, the odds of the
> >Live image doing something different seem pretty slim.
> >
> >I agree with Felix's recommendation to post information about the
> >graphics card and at least the Jessie X log file (having both the Jessie
> >and Wheezy log files would be better).
> >
> >regards,
> >mike
> I have a copy of Xorg.0.log for both Wheezy and Jessie.  How do I post them
> to paste.debian.net?

Please post them to the mailing list for future info.
It's only Felix who suggests that, you've been on the list long enough
to know that logs are sent with the emails.

--
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the
oppressing." --- Malcolm X

Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

Marc Shapiro-3
On 12/01/2015 04:15 AM, Chris Bannister wrote:

> On Mon, Nov 30, 2015 at 05:10:33PM -0800, Marc Shapiro wrote:
>> On 11/30/2015 04:45 PM, Mike Kupfer wrote:
>>> Marc Shapiro wrote:
>>>
>>>> On 11/30/2015 04:01 PM, Mike Kupfer wrote:
>>>>> - Boot a Live image and see what resolution it gives you.
>>>> I can still boot into Wheezy and get 1920x1080.
>>> I meant a Jessie Live image.
>>>
>>> Though given that you didn't find an old xorg.conf file, the odds of the
>>> Live image doing something different seem pretty slim.
>>>
>>> I agree with Felix's recommendation to post information about the
>>> graphics card and at least the Jessie X log file (having both the Jessie
>>> and Wheezy log files would be better).
>>>
>>> regards,
>>> mike
>> I have a copy of Xorg.0.log for both Wheezy and Jessie.  How do I post them
>> to paste.debian.net?
> Please post them to the mailing list for future info.
> It's only Felix who suggests that, you've been on the list long enough
> to know that logs are sent with the emails.
>
I have posted them to the list.  My post of Nov. 30 (yesterday) at 5:27
PM PDT contains the full content of both log files.

Marc

Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

Sven Arvidsson
In reply to this post by Marc Shapiro-3
On Mon, 2015-11-30 at 23:11 -0800, Marc Shapiro wrote:

> In Wheezy, the graphics card seems to have been found and a depth of
> 24bpp is being used by RADEON(0) with a GB of graphics memory, while
> in
> Jessie, Screen 0 is getting deleted and the radeon module is removed.
>  
> Instead of RADEON(0) we see FBDEV(0), instead of 24bbp, only 16bbp is
> being used.  Only 1536kB of video memory is being used and the screen
> size is set to "Virtual size is 1024x768 (pitch 1024)".
>
> I don't know enough to determine what is causing these differences,
> let
> alone how to correct the problem.  If someone else can figure out a
> solution I would be most grateful.
Most likely missing firmware as others have suggested, check dmesg and
grep for radeon and/or drm.

--
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5




signature.asc (836 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade to Jessie lost all monitor resolutions except 1024x768

Marc Shapiro-3
On 12/01/2015 07:03 AM, Sven Arvidsson wrote:

> On Mon, 2015-11-30 at 23:11 -0800, Marc Shapiro wrote:
>> In Wheezy, the graphics card seems to have been found and a depth of
>> 24bpp is being used by RADEON(0) with a GB of graphics memory, while
>> in
>> Jessie, Screen 0 is getting deleted and the radeon module is removed.
>>    
>> Instead of RADEON(0) we see FBDEV(0), instead of 24bbp, only 16bbp is
>> being used.  Only 1536kB of video memory is being used and the screen
>> size is set to "Virtual size is 1024x768 (pitch 1024)".
>>
>> I don't know enough to determine what is causing these differences,
>> let
>> alone how to correct the problem.  If someone else can figure out a
>> solution I would be most grateful.
> Most likely missing firmware as others have suggested, check dmesg and
> grep for radeon and/or drm.
>
I will install  firmware-amd-graphics as soon as I get a chance
(probably this evening) and report back.  Meanwhile, Felix says that he
never received my post with the full logs and others seem not to have
received them, either, by what they have posted.  For the sake of
keeping all of the information available for the future, I will post
them at that time, as well.  Should they be sent as attachments, or
inline.  I sent them as attachments last time. Could that have been the
problem?

Marc

12