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


Groups > linux.debian.kernel > #53795

Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple"

From Ben Hutchings <ben@decadent.org.uk>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple"
Date 2016-04-27 11:50 +0200
Message-ID <rsugx-7q8-1@gated-at.bofh.it> (permalink)
References (1 earlier) <rs6Hf-4gv-17@gated-at.bofh.it> <rs8g1-5TZ-13@gated-at.bofh.it> <rsaBc-7X7-7@gated-at.bofh.it> <rsbQC-Gm-23@gated-at.bofh.it> <rsrLI-5uN-27@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Control: tag -1 - moreinfo

On Wed, 2016-04-27 at 09:01 +0200, Harald Dunkel wrote:
> On 04/26/2016 04:05 PM, Ben Hutchings wrote:
> > 
> > 
> > I'm guessing that you didn't built the mgag200 driver
> > (CONFIG_DRM_MGA),
> > right?
> > 
> Of course its in, as for the official kernel.
> 
> 	% grep -i mga /boot/config-4.5.2
> 	CONFIG_DRM_MGA=m
> 	CONFIG_DRM_MGAG200=m

Oh of course, mga and mgag200 are two different drivers.  Thanks for
working out what I meant.

> Would you suggest to blacklist this module?

Not in general, but that should work around the bug.  That is
effectively what we were doing before version 4.4~rc5-1~exp1 to avoid
conflicts with older X drivers (while xserver-xorg-video-modesetting
would override that blacklisting).  Since we don't patch mgag200 any
more, I don't understand why you are seeing a bug with the official
kernel package and yet not with a custom kernel.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Back to linux.debian.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: Bug#822575: debian regression: no more console output after  "switching to mgag200drmfb from simple" Mattia Rizzolo <mattia@debian.org> - 2016-04-26 10:40 +0200
  Processed: Re: Bug#822575: debian regression: no more console  output after "switching to mgag200drmfb from simple" owner@bugs.debian.org (Debian Bug Tracking System) - 2016-04-26 10:40 +0200
  Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple" Ben Hutchings <ben@decadent.org.uk> - 2016-04-26 12:20 +0200
    Re: Bug#822575: debian regression: no more console output after  "switching to mgag200drmfb from simple" Harald Dunkel <harald.dunkel@aixigo.de> - 2016-04-26 14:00 +0200
    Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple" Harald Dunkel <harald.dunkel@aixigo.de> - 2016-04-26 14:50 +0200
      Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple" Ben Hutchings <ben@decadent.org.uk> - 2016-04-26 16:10 +0200
        Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple" Harald Dunkel <harald.dunkel@aixigo.de> - 2016-04-27 09:10 +0200
          Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple" Ben Hutchings <ben@decadent.org.uk> - 2016-04-27 11:50 +0200
  Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple" Harald Dunkel <harald.dunkel@aixigo.de> - 2016-04-26 14:40 +0200

csiph-web