From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Need help getting started with X11
Date: Mon, 24 Nov 2014 21:07:22 +0100 [thread overview]
Message-ID: <20141124210722.49239966@free-electrons.com> (raw)
In-Reply-To: <CAEzGmjByqb2QB4+-QDOcJYDo6zvD+UpkG9kaNmBzBHKMFaGDJg@mail.gmail.com>
Dear Lennart Ramberg,
On Mon, 24 Nov 2014 13:41:38 +0100, Lennart Ramberg wrote:
> Or, if anyone would be so kind, I'm stuck at the below defconfig.
> The system works in the sense that I can ssh into it, but now I want
> graphics on the console display.
> I have not yet anything in the overlays that starts or otherwise relates to
> xorg.
> My target chipset is Intel 852GM.
> For one thing, what is supposed to create an xorg.conf?
These days, if you enable udev a xorg.conf is often not needed.
> And I suppose X should be started somehow in supervisor.d like I start sshd
> there.
>
> BR2_x86_i686=y
> BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
> # BR2_TARGET_GENERIC_GETTY is not set
> BR2_ROOTFS_OVERLAY="board/eta/board1/rootfs-overlay/"
> BR2_LINUX_KERNEL=y
> BR2_LINUX_KERNEL_DEFCONFIG="i386"
> BR2_LINUX_KERNEL_INSTALL_TARGET=y
> BR2_PACKAGE_XORG7=y
> BR2_PACKAGE_XSERVER_XORG_SERVER=y
Make sure to also enable the Intel graphics driver, i.e.
BR2_PACKAGE_XDRIVER_XF86_VIDEO_INTEL. Note that you need to switch the
"modular X.org server" variant to achieve that.
And then, start the X server by simply running "X".
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-24 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 12:41 [Buildroot] Need help getting started with X11 Lennart Ramberg
2014-11-24 20:07 ` Thomas Petazzoni [this message]
2014-11-25 10:50 ` Lennart Ramberg
2014-11-25 18:02 ` Thomas Petazzoni
2014-11-26 16:47 ` Lennart Ramberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141124210722.49239966@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox