<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Mageia support for GMA 3600 (Cedar Trail Atom)
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mageia%20support%20for%20GMA%203600%20%28Cedar%20Trail%20Atom%29&In-Reply-To=%3CPine.LNX.4.44.1203112103390.8432-100000%40outpost-priv%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="012877.html">
<LINK REL="Next" HREF="012956.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Mageia support for GMA 3600 (Cedar Trail Atom)</H1>
<B>tux99-mga at uridium.org</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mageia%20support%20for%20GMA%203600%20%28Cedar%20Trail%20Atom%29&In-Reply-To=%3CPine.LNX.4.44.1203112103390.8432-100000%40outpost-priv%3E"
TITLE="[Mageia-dev] Mageia support for GMA 3600 (Cedar Trail Atom)">tux99-mga at uridium.org
</A><BR>
<I>Sun Mar 11 21:22:32 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="012877.html">[Mageia-dev] Mageia support for GMA 3600 (Cedar Trail Atom)
</A></li>
<LI>Next message: <A HREF="012956.html">[Mageia-dev] Mageia support for GMA 3600 (Cedar Trail Atom)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#12951">[ date ]</a>
<a href="thread.html#12951">[ thread ]</a>
<a href="subject.html#12951">[ subject ]</a>
<a href="author.html#12951">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Fri, 9 Mar 2012 <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">tux99-mga at uridium.org</A> wrote:
><i> On Fri, 9 Mar 2012, Thomas Backlund wrote:
</I>><i>
</I>><i> > <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">tux99-mga at uridium.org</A> skrev 8.3.2012 02:18:
</I>><i> > >
</I>><i> > > Hi,
</I>><i> > > I just tried Mageia 2 beta 1 on a Intel DN2800MT board hoping that it
</I>><i> > > would have framebuffer support for the GMA 3600, but the attached
</I>><i> > > monitor goes into standby (no signal) as soon as the frame buffer gets
</I>><i> > > activated during boot.
</I>><i> > >
</I>><i> > > As far as I understand there is frame buffer support in the 3.3 kernel
</I>><i> > > for the GMA 3600 so in theory it should work.
</I>><i> > >
</I>><i> > > Are you aware of this issue or should I do a bug report?
</I>><i> >
</I>><i> > Yes.
</I>><i> >
</I>><i> > There is a bug with Cedar Trail that got fixed upstream a few days after
</I>><i> > 3.3-rc6 was released, so the fix is not in our current
</I>><i> > kernel-3.3.0-0.rc6.1.mga2, but it will be fixed in the next build.
</I>><i>
</I>><i> Thanks, that's great, I will test the next build and then report back
</I>><i> how that works with my Cedar Trail board.
</I>
Hi, I noticed a new kernel packages showed up in the cauldron repo
(3.3rc7) so I tried it immediately (reinstalled cauldron from scratch as
I had overwritten the previous install with other distro tests) using
the boot.iso image, but the video behaviour at boot is still the same,
the monitor still goes into no-signal standby as soon as the drm stuff
is started.
I have full access to the box via ssh so I have uploaded some logs that
might help figure this out, it looks to like the kernel modules load
fine but somehow they set a screen mode that the monitor doesn't like.
Basically I don't really know how the drm kernel modules and xorg
interact (and I can't find any useful recent docs about it), who is
responsible for setting the screen mode and where can I manually
configure it, on the kernel line or xorg.conf?
(I have been spoiled by the binary nvidia drivers for too long :) )
dmesg:
<A HREF="http://pastebin.com/SLBcgjXx">http://pastebin.com/SLBcgjXx</A>
lsmod output:
# lsmod|grep gma
gma500_gfx 149940 0
drm_kms_helper 32743 1 gma500_gfx
drm 207700 2 gma500_gfx,drm_kms_helper
i2c_algo_bit 13080 1 gma500_gfx
i2c_core 29836 5
i2c_i801,gma500_gfx,drm_kms_helper,drm,i2c_algo_bit
video 18640 1 gma500_gfx
/var/log/Xorg.0.log:
<A HREF="http://pastebin.com/ypw0DAnz">http://pastebin.com/ypw0DAnz</A>
I'm unsure if this is only a config problem or if this is still due
to some bug.
Any pointers would be much appreciated.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="012877.html">[Mageia-dev] Mageia support for GMA 3600 (Cedar Trail Atom)
</A></li>
<LI>Next message: <A HREF="012956.html">[Mageia-dev] Mageia support for GMA 3600 (Cedar Trail Atom)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#12951">[ date ]</a>
<a href="thread.html#12951">[ thread ]</a>
<a href="subject.html#12951">[ subject ]</a>
<a href="author.html#12951">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>