[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

mgag200: Anyone seen this off-by-N error before?



Hi all,

I'm currently picking fights with this Dell PowerEdge R320 server that
we're setting up for an energy management project.

I found the machine would successfully install Debian Jessie i386, but
then would immediately kernel panic on the first boot.  We use the i386
version because the SCADA software we use requires it.

After trying a few things to no avail, I broke down and installed the
AMD64 version, figuring I'll use either LXC or KVM to run a i386 guest.
 That worked, and the machine successfully boots.  HOWEVER, I was
confronted by this:

http://www.longlandclan.yi.org/~stuartl/debian-user/2015/06/30-mgag200/x.png

The console is similarly affected:

http://www.longlandclan.yi.org/~stuartl/debian-user/2015/06/30-mgag200/console-fb.png

It seems there's an off-by-N error in the framebuffer, which makes the
console pretty much unreadable.  I tried downloading this kernel package:

https://packages.debian.org/sid/amd64/linux-image-4.0.0-2-amd64

and installing that, I get the same problem (and lxc doesn't work).  So
I'm back on the stock Jessie kernel 3.16.7-ckt11-1
(linux-image-amd64_3.16+63_amd64.deb), and I've gotten by creating
/etc/modprobe.d/blacklist-mgag200.conf:

> blacklist mgag200

That gets things working, although I notice there's now no acceleration
in X, we can live with that as its only purpose is to allow interaction
with virt-manager (for KVM).

The details of the offending video device:
> 06:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. G200eR2 (prog-if 00 [VGA controller])
>         Subsystem: Dell Device 04f7
>         Flags: bus master, medium devsel, latency 64, IRQ 11
>         Memory at d8000000 (32-bit, prefetchable) [size=16M]
>         Memory at de7fc000 (32-bit, non-prefetchable) [size=16K]
>         Memory at dd800000 (32-bit, non-prefetchable) [size=8M]
>         Expansion ROM at <unassigned> [disabled]
>         Capabilities: [dc] Power Management version 1

Has anyone seen this bug with this driver and/or have any ideas I could try?

Regards,
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.


Reply to: